Skip to main content
Glama
Bitget-AI

Bitget Agent MCP

Official
by Bitget-AI

order

Manage crypto trade operations with a single command: place, cancel, modify, batch, cancel all, countdown auto-cancel, and fetch open, detail, history, and fills.

Instructions

[VERB] Manage orders by intent: place/cancel/modify (single or batch via orders), cancelAll, countdownCancel, plus open/detail/history/fills reads. Writes honor dryRun/confirm/readOnly; cancelAll requires confirm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyNoOrder size/quantity (the v3 API field name).
sideNobuy or sell.
viewNosummary (default) trims null fields to save tokens; full returns the untouched payload.
limitNoLimit per page Default:100. Maximum:100
priceNoOrder price (limit orders).
actionYesWhat to do — place: place an order (needs: category, symbol, qty, side, orderType) | cancel: cancel an order | modify: modify an order | cancelAll: cancel all orders (destructive) (needs: category) | countdownCancel: dead-man's-switch auto-cancel (needs: countdown) | open: list open orders | detail: one order's detail | history: historical orders (needs: category) | fills: fill history | maxOpen: max openable size (needs: category, symbol, orderType, side). Pass `orders` to batch place/cancel/modify.
cursorNoCursor Pagination is implemented by omitting the cursor in the first query and applying the cursor from the previous query for subsequent pages
dryRunNoPreview the write without sending it.
fieldsNoOptional list (array or comma-separated string) of fields to keep on each returned row.
ordersNoArray of order/cancel/modify objects. When present, place/cancel/modify route to the batch endpoint automatically.
symbolNoTrading pair, e.g. BTCUSDT.
confirmNoRequired to execute cancelAll (destructive).
endTimeNoEnd timestamp A Unix timestamp in milliseconds e.g.,1597026383085
orderIdNoTarget order id for cancel/modify/detail.
posSideNoPosition side long/short This field is required in hedge-mode position. Available only for futures
stpModeNoSTP Mode(Self Trade Prevention) none: not setting STP(default) cancel_taker: cancel taker order cancel_maker: cancel maker order cancel_both: cancel both of taker and maker orders
categoryNoProduct category, e.g. SPOT or USDT-FUTURES.
fetchAllNohistory/fills only: walk the cursor to bounded completion (returns { items, pages, truncated }).
stopLossNoPreset Stop-Loss Trigger Price
clientOidNoIdempotency key. Auto-generated for a single `place` when omitted (P7).
countdownNoReconnect Window - Unit: seconds - Positive integer, range: [5, 60]. The minimum countdown is 5 second, and the maximum is 60 seconds. Filling in 0 cancels the countdown order cancellation function.
orderTypeNolimit or market.
startTimeNoStart timestamp A Unix timestamp in milliseconds e.g.,1597026383085
autoCancelNoWill the original order be canceled if the order modification fails yes: Cancel no: Not cancel(default)
reduceOnlyNoReduce-only identifier yes/no, default no; yes indicates that your position may only be reduced in size upon the activation of this order
takeProfitNoPreset Take-Profit Trigger Price
slOrderTypeNoStop-Loss Trigger Strategy Order Type limit: Limit Order market: Market Order
slTriggerByNoPreset Stop-Loss Trigger Type market: Market Price mark: Mark Price If not filled in, the default value is market price Note: This field is only valid for the contract business lines: USDT-Futures, COIN-Futures, and USDC-Futures
timeInForceNoTime in force ioc Immediate or cancel. It must be executed immediately, with any unfilled portion canceled. fok Fill or kill. It must be fully executed immediately, or it is canceled entirely. gtc Good 'til canceled. It remains active until it is either filled or manually canceled. post_only Post only. It will only be added to the order book as a maker. This field is required when orderType is limit. If omitted, it defaults to gtc
tpOrderTypeNoTake-Profit Trigger Strategy Order Type limit: Limit Order market: Market Order
tpTriggerByNoPreset Take-Profit Trigger Type market: Market Price mark: Mark Price If not specified, the default value is market price Note: This field is only valid for the contract business lines: USDT-Futures, COIN-Futures, and USDC-Futures.
slLimitPriceNoStop-Loss Strategy Order Execution Price This field is only valid for limit orders (when slOrderType=limit); it is ignored for market orders.
tpLimitPriceNoTake-Profit Strategy Order Execution Price This field is only valid for limit orders (when tpOrderType=limit); it is ignored for market orders.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations, the description discloses important behaviors: writes honor dryRun/confirm/readOnly, and cancelAll requires confirm. This adds context about safety gates and destructive actions. The mention of reads clarifies which actions are non-mutating.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, two sentences, and front-loaded with the core purpose. The list of actions is necessary. Minor penalty for the '[VERB]' placeholder artifact and the mention of 'readOnly' which is not in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 33 parameters and no output schema, the description provides only a high-level overview. It lacks information about return values or per-action output expectations. The schema covers parameter details, but the description doesn't explain what the agent should expect from open/detail/history/fills.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds semantics for the `orders` parameter (batch) and the confirm requirement for cancelAll, which goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool manages orders, listing specific actions such as place/cancel/modify, batch support, cancelAll, countdownCancel, and read operations. This is a specific verb+resource that distinguishes it from sibling tools like strategy_order, market, and position.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for order management but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or alternative tools. The list of operations gives context, but no sibling differentiation is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bitget-AI/agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server