Skip to main content
Glama
iuk-ink

Binance MCP Server

by iuk-ink

futures_order

Place Binance futures orders with limit, market, stop loss, take profit, and trailing stop market types. Supports hedging mode and position closing.

Instructions

期货下单(限价/市价/止损/止盈/跟踪止损等)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes交易对符号
sideYes买卖方向
positionSideNo持仓方向。账户处于双向持仓模式(Hedge Mode)时此参数必填,不传会报错
typeYes订单类型。平仓建议:市价平仓=MARKET+SELL,止损平仓=STOP_MARKET+closePosition=true,止盈平仓=TAKE_PROFIT_MARKET+closePosition=true
quantityYes数量(平仓止损止盈时用 closePosition=true 替代,无需传 quantity)
priceNo价格(LIMIT/STOP 限价单必需)
timeInForceNo有效期(仅 LIMIT 生效)GTC
reduceOnlyNo仅减仓(Hedge 模式下 SELL+LONG 会自动设为 true,无需手动传,传了反而可能报 not required)
stopPriceNo触发价(STOP/STOP_MARKET/TAKE_PROFIT_MARKET 必需)
activationPriceNo激活价格(TRAILING_STOP_MARKET 必需)。Binance 可能自动修正此值,最终生效价以返回的 activatePrice 为准
callbackRateNo回调幅度百分比(TRAILING_STOP_MARKET 必需,如"1"表示 1%)
workingTypeNo触发价类型CONTRACT_PRICE
closePositionNo全仓平仓(仅 STOP_MARKET/TAKE_PROFIT_MARKET 支持,不支持 MARKET/LIMIT/TRAILING_STOP_MARKET)
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as idempotency, rate limits, or required permissions. Some parameter behaviors are detailed in the schema, but the tool description itself is silent on these aspects.

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

Conciseness3/5

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

The description is very short (one line in Chinese) but lacks structure or prioritization. It is concise but could be better organized with key information front-loaded.

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

Completeness2/5

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

Given the tool's complexity (13 parameters, many order types) and no output schema, the description is incomplete. It does not cover return values, error handling, or how to check order status. Though parameter descriptions help, the overall description fails to provide sufficient context for effective usage.

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 description coverage is 100%, and parameter descriptions are detailed with usage notes (e.g., closePosition restrictions, reduceOnly auto-setting). The tool description adds no additional parameter information beyond the schema, resulting in baseline score.

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 handles futures orders with multiple order types (limit, market, stop, take profit, trailing stop). It is specific and distinct from sibling tools like balance, market data, and quick order.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like futures_quick_order. The description only lists order types without explaining selection criteria or when not to use the tool.

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/iuk-ink/binance-mcp-server'

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