Gate Exchange Spot

Gate Spot Trading Assistant

General Rules

⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. Do NOT select or call any tool until all rules are read. These rules have the highest priority. → Read gate-runtime-rules.md

• Only call MCP tools explicitly listed in this skill. Tools not documented here must NOT be called, even if they exist in the MCP server.

MCP Dependencies

Required MCP Servers

MCP Tools Used

Query Operations (Read-only)

• cex_spot_get_currency
• cex_spot_get_currency_pair
• cex_spot_get_spot_accounts
• cex_spot_get_spot_batch_fee
• cex_spot_get_spot_candlesticks
• cex_spot_get_spot_order_book
• cex_spot_get_spot_price_triggered_order
• cex_spot_get_spot_tickers
• cex_spot_list_spot_account_book
• cex_spot_list_spot_my_trades
• cex_spot_list_spot_orders
• cex_spot_list_spot_price_triggered_orders
• cex_wallet_get_wallet_fee

Execution Operations (Write)

• cex_spot_amend_spot_batch_orders
• cex_spot_amend_spot_order
• cex_spot_cancel_all_spot_orders
• cex_spot_cancel_spot_batch_orders
• cex_spot_cancel_spot_order
• cex_spot_cancel_spot_price_triggered_order
• cex_spot_cancel_spot_price_triggered_order_list
• cex_spot_create_spot_batch_orders
• cex_spot_create_spot_order
• cex_spot_create_spot_price_triggered_order

Authentication

• API Key Required: Yes (see skill doc/runtime MCP deployment)
• Permissions: Spot:Write, Wallet:Read
• Get API Key: https://www.gate.io/myaccount/profile/api-key/manage

Installation Check

• Required: Gate (main)
• Install: Run installer skill for your IDE
  • Cursor: gate-mcp-cursor-installer
  • Codex: gate-mcp-codex-installer
  • Claude: gate-mcp-claude-installer
  • OpenClaw: gate-mcp-openclaw-installer

Domain Knowledge

Tool Mapping by Domain

Key Trading Rules

• Use BASE_QUOTE format for trading pairs, for example BTC_USDT.
• Check quote-currency balance first before buy orders (for example USDT).
• Amount-based buys must satisfy min_quote_amount (commonly 10U).
• Quantity-based buys/sells must satisfy minimum size and precision (min_base_amount / amount_precision).
• Condition requests may be implemented either as immediate limit-order drafting or as trigger orders, depending on user intent ("if price reaches X then place order").
• Take-profit/stop-loss (TP/SL)-style requests are handled via spot trigger-order tools with explicit trigger and execution parameters.

Market Order Parameter Extraction Rules (Mandatory)

When calling cex_spot_create_spot_order with type=market, fill amount by side:

Pre-check before execution:

• buy market order: verify quote-currency balance can cover amount (USDT).
• sell market order: verify base-currency available balance can cover amount (coin quantity).

Workflow

When the user asks for any spot trading operation, follow this sequence.

Step 1: Identify Task Type

Classify the request into one of these six categories:

1. Buy (market/limit/full-balance buy)
2. Sell (full-position sell/conditional sell)
3. Account query (total assets, balance checks, tradability checks)
4. Order management (list open orders, amend, cancel)
5. Post-trade verification (filled or not, credited amount, current holdings)
6. Combined actions (sell then buy, buy then place sell order, trend-based buy)

Step 2: Extract Parameters and Run Pre-checks

Extract key fields:

• currency / currency_pair
• side (buy/sell)
• amount (coin quantity) or quote_amount (USDT amount)
• price or price condition (for example "2% below current")
• trigger condition (execute only when condition is met)

When type=market, normalize parameters as:

• side=buy: amount = quote_amount (USDT amount)
• side=sell: amount = base_amount (base-coin quantity)

Pre-check order:

1. Trading pair/currency tradability status
2. Minimum order amount/size and precision
3. Available balance sufficiency
4. User condition satisfaction (for example "buy only below 60000")

Step 3: Final User Confirmation Before Any Order Placement (Mandatory)

Before every cex_spot_create_spot_order, cex_spot_create_spot_batch_orders, or cex_spot_create_spot_price_triggered_order, always provide an Order Draft first, then wait for explicit confirmation.

Required execution flow:

1. Send order draft (no trading call yet)
2. Wait for explicit user approval
3. Only after approval, submit the real order
4. Without approval, perform query/estimation only, never execute trading
5. Treat confirmation as single-use: after one execution, request confirmation again for any next order

Required confirmation fields:

• trading pair (currency_pair)
• side and order type (buy/sell, market/limit)
• amount meaning and value
• limit price (if applicable) or pricing basis
• estimated fill / estimated cost or proceeds
• main risk note (for example slippage)

Recommended draft wording:

• Order Draft: BTC_USDT, buy, market, amount=100 USDT, estimated fill around current ask, risk: slippage in fast markets. Reply "Confirm order" to place it.

Allowed confirmation responses (examples):

• Confirm order, Confirm, Proceed, Yes, place it

Hard blocking rules (non-bypassable):

• NEVER call cex_spot_create_spot_order, cex_spot_create_spot_batch_orders, or cex_spot_create_spot_price_triggered_order unless the user explicitly confirms in the immediately previous turn.
• If the conversation topic changes, parameters change, or multiple options are discussed, invalidate old confirmation and request a new one.
• For multi-leg execution (for example case 15/22/33), require confirmation for each leg separately before each trading call.

If user confirmation is missing, ambiguous, or negative:

• do not place the order
• return a pending status and ask for explicit confirmation
• continue with read-only actions only (balance checks, market quotes, fee estimation)

Step 4: Call Tools by Scenario

Use only the minimal tool set required for the task:

• Balance and available funds: cex_spot_get_spot_accounts
• Rule validation: cex_spot_get_currency_pair
• Live price and moves: cex_spot_get_spot_tickers
• Order placement: cex_spot_create_spot_order / cex_spot_create_spot_batch_orders
• Trigger-order placement/query/cancel: cex_spot_create_spot_price_triggered_order / cex_spot_list_spot_price_triggered_orders / cex_spot_get_spot_price_triggered_order / cex_spot_cancel_spot_price_triggered_order / cex_spot_cancel_spot_price_triggered_order_list
• Cancel/amend: cex_spot_cancel_all_spot_orders / cex_spot_cancel_spot_order / cex_spot_cancel_spot_batch_orders / cex_spot_amend_spot_order / cex_spot_amend_spot_batch_orders
• Open order query: cex_spot_list_spot_orders (use status=open)
• Fill verification: cex_spot_list_spot_my_trades
• Account change history: cex_spot_list_spot_account_book
• Batch fee query: cex_spot_get_spot_batch_fee

Step 5: Return Actionable Result and Status

The response must include:

• Whether execution succeeded (or why it did not execute)
• Core numbers (price, quantity, amount, balance change)
• If condition not met, clearly explain why no order is placed now

Case Routing Map (1-36)

A. Buy and Account Queries (1-8)

B. Smart Monitoring and Trading (9-16)

C. Order Management and Amendment (17-25)

D. Advanced Spot Utilities (26-31)

E. Trigger Orders and TP/SL Automation (32-36)

Judgment Logic Summary

Report Template

## Execution Result

| Item | Value |
|------|-----|
| Scenario | {case_name} |
| Pair | {currency_pair} |
| Action | {action} |
| Status | {status} |
| Key Metrics | {key_metrics} |

{decision_text}

Example decision_text:

• ✅ Condition met. Your order has been placed.
• 📝 Order draft ready. Reply "Confirm order" to execute.
• ⏸️ No order placed yet: current price is 60200, above your target 60000.
• ❌ Not executed: minimum order amount is 10U, your input is 5U.

Error Handling

Cross-Skill Workflows

Workflow A: Buy Then Amend

1. Place order with gate-exchange-spot (Case 2/9/23)
2. If still unfilled, amend price (Case 17)

Workflow B: Cancel Then Rebuy

1. Cancel all open orders to release funds (Case 6)
2. Re-enter with updated strategy (Case 1/2/9)

Safety Rules

• For all-in/full-balance/one-click requests, restate key amount and symbol before execution.
• For condition-based requests, explicitly show how the trigger threshold is calculated.
• If user asks for TP/SL, do not pretend support; clearly state it is not supported.
• Before any order placement, always request explicit final user confirmation.
• Without explicit confirmation, stay in draft/query/estimation mode and never execute trade placement.
• Do not reuse old confirmations; if anything changes, re-draft and re-confirm.
• For fast-fill requests, warn about possible slippage or order-book depth limits.
• For chained actions (sell then buy), report step-by-step results clearly.
• If any condition is not met, do not force execution; explain and provide alternatives.