Skip to main content
Glama
Bitget-AI

Bitget Agent MCP

Official
by Bitget-AI

strategy_order

Place, cancel, modify, list open, and review crypto strategy orders (take-profit/stop-loss). Supports dry-run and confirmation for safe writes.

Instructions

[VERB] Strategy (trigger/plan) orders by intent: place | cancel | modify | open (unfilled) | history. Writes honor dryRun/confirm/readOnly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qtyNoOrder Quantity This is a required field when tpslMode=partial, and the unit is in the base coin
typeNoStrategy Type tpslTake-Profit and Stop-Loss Default:tpsl
viewNosummary (default) trims null fields to save tokens; full returns the untouched payload.
limitNoLimit per page Default:100. Maximum:100
actionYesWhat to do — place: create a strategy order (needs: category, symbol, qty, posSide) | cancel: cancel a strategy order (needs: orderId) | modify: modify a strategy order (needs: orderId, qty) | open: list unfilled strategy orders (needs: category) | history: strategy order history (needs: category).
cursorNoCursor Pagination is implemented by omitting the cursor in the first query and applying the cursor from the previous query for subsequent pages
dryRunNoPreview a write without sending it.
fieldsNoOptional list (array or comma-separated string) of fields to keep on each returned row.
symbolNoTrading pair, e.g. BTCUSDT.
confirmNoRequired to execute destructive (high-risk) writes; without it such a call returns { confirmationRequired: true }.
endTimeNoEnd timestamp A Unix timestamp in milliseconds e.g.,1597026383085
orderIdNoTarget strategy order id for cancel/modify.
posSideNoPosition side long/short
categoryNoProduct category, e.g. USDT-FUTURES.
fetchAllNoPaged reads only: walk the cursor to bounded completion (returns { items, pages, truncated }).
stopLossNoStop-Loss Trigger Price
tpslModeNoTake-Profit and Stop-Loss Mode fullAll Positions Take-Profit and Stop-Loss partialPartial Position Take-Profit and Stop-Loss If left blank, the default value is full
clientOidNoIdempotency key. Auto-generated for `place` when omitted (P7).
startTimeNoStart timestamp A Unix timestamp in milliseconds e.g.,1597026383085
takeProfitNoTake-Profit Trigger Price
slOrderTypeNoStop-Loss Trigger Strategy Order Type limit: Limit Order market: Market Order If not filled in, the default value is market price
slTriggerByNoStop-Loss Trigger Type market: Market Price mark: Mark Price If not filled in, the default value is market price
tpOrderTypeNoTake-Profit Trigger Strategy Order Type limit: Limit Order market: Market Order If not filled in, the default value is market price
tpTriggerByNoTake-Profit Trigger Type market: Market Price mark: Mark Price If not specified, the default value is market price
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?

Annotations already declare readOnlyHint=false, and the description usefully adds that writes honor dryRun/confirm/readOnly, clarifying preview and confirmation behavior for a mutation-capable tool. It does not disclose response shapes, error semantics, or auth requirements, but the added safety-flag context goes beyond the annotations.

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 extremely concise and front-loaded with the core intents, with zero filler. The '[VERB]' placeholder is an unnecessary artifact, but for a tool with 26 parameters, this brevity keeps the most important information accessible.

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?

Given the tool's complexity (26 parameters, no output schema), the description is thin: it names intents and safety behavior but does not explain return-value conventions, how to map actions to required parameters, or pagination behavior. The schema's rich per-parameter descriptions partially compensate, making it minimally viable but not complete.

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

Parameters3/5

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

Schema coverage for parameters is 100%, and each parameter already has detailed descriptions and enums, including action-specific remarks in the 'action' parameter. The tool description itself adds no parameter-level information beyond listing high-level intents, so the baseline 3 is appropriate.

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

Purpose4/5

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

The description identifies the resource as strategy (trigger/plan) orders and enumerates the five distinct intents (place, cancel, modify, open, history), which clearly distinguishes it from sibling tools like 'order'. The literal '[VERB]' placeholder is a formatting flaw, but the action list makes the purpose specific and actionable.

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?

It implicitly scopes the tool to strategy trigger/plan orders versus normal orders, and the 'writes honor dryRun/confirm/readOnly' note gives some operational context. However, it never explicitly states when to prefer this tool over a sibling like 'order' or 'market', nor does it list exclusions or prerequisites.

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