Binance MCP Server

下单

trading_place_order

Destructive

Place Binance futures orders with automatic precision rounding, dry-run validation, and hedge mode support. Specify symbol, side, type, quantity; optional price, reduceOnly, timeInForce, positionSide.

Instructions

下单（自动精度规整）。dryRun=true 时仅校验不提交。reduceOnly 仅单向模式可用。timeInForce 为 GTD 时必须提供 goodTillDate。持仓模式约束：单向省略 positionSide，双向（Hedge）必须传 positionSide（LONG/SHORT），可用 trading_position_mode 查询。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "side": "<side>",
      "type": "<type>",
      "quantity": "<quantity>"
    },
    "name": "trading_place_order"
  }
}

Input Schema

Name	Required	Description	Default
`side`	Yes
`type`	Yes
`price`	No
`dryRun`	No
`symbol`	Yes
`quantity`	Yes
`reduceOnly`	No
`timeInForce`	No
`goodTillDate`	No
`positionSide`	No
`newClientOrderId`	No
`newOrderRespType`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv3.0.1Aug 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / dryRun

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / goodTillDate

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedInput schema / properties / newClientOrderId
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / newOrderRespType

Added value: +{
+  "enum": [
+    "ACK",
+    "RESULT"
+  ],
+  "type": "string"
+}

removedInput schema / properties / positionSide / description

Removed value: -"持仓方向（双向持仓模式时需指定）"

changedInput schema / properties / positionSide / enum

Previous value: -[
-  "BOTH",
-  "LONG",
-  "SHORT"
-]New value: +[
+  "LONG",
+  "SHORT"
+]

removedInput schema / properties / price / description
```
Removed value: -"价格(市价可不传)"
```
removedInput schema / properties / quantity / description
```
Removed value: -"数量(市价全仓可不传)"
```
removedInput schema / properties / reduceOnly / description
```
Removed value: -"仅减仓 true=是"
```
removedInput schema / properties / side / description
```
Removed value: -"方向 BUY=买入 / SELL=卖出"
```

removedInput schema / properties / stopPrice

Removed value: -{
-  "description": "止损/止盈触发价",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}

removedInput schema / properties / symbol / description
```
Removed value: -"交易对符号 如 BTCUSDT"
```

removedInput schema / properties / timeInForce / description

Removed value: -"有效期 GTC=有效至取消 / IOC=立即成交或取消 / FOK=全部成交或取消"

changedInput schema / properties / timeInForce / enum

Previous value: -[
-  "GTC",
-  "IOC",
-  "FOK",
-  "GTX",
-  "GTD"
-]New value: +[
+  "GTC",
+  "IOC",
+  "FOK",
+  "GTX",
+  "GTD",
+  "RPI"
+]

changedInput schema / properties / type / enum

Previous value: -[
-  "LIMIT",
-  "MARKET",
-  "STOP",
-  "STOP_MARKET",
-  "TAKE_PROFIT",
-  "TAKE_PROFIT_MARKET",
-  "TRAILING_STOP_MARKET"
-]New value: +[
+  "LIMIT",
+  "MARKET"
+]

changedInput schema / required

Previous value: -[
-  "symbol",
-  "side",
-  "type"
-]New value: +[
+  "symbol",
+  "side",
+  "type",
+  "quantity"
+]

Addedv2.0.3Jun 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

注解已声明 readOnlyHint=false 和 destructivedestination，描述在此基础上补充了实际行为：自动精度规整、dryRun 的只校验不提交语义、reduceOnly 的模式限制，以及持仓模式对 positionSide 的约束。这些信息超出注解本身，帮助 agent 理解操作的动态规则，但未未涉及真实下单后的资金/保证金锁定等后果，属于适度而不是完全透明。

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

Conciseness5/5

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

描述由五个短句组成，用分散号清晰分隔，重要的一次性校验与模式约束前置，没有冗余修饰。每条信息都对应一个可操作约束，结构紧凑高效，符合高分标准。

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?

这是一个 12 个参数、无输出 schema、无参数描述、带 destructiveHint 的复杂资金操作工具。描述虽然覆盖了主要约束,但缺少 LIMIT/MARKET 与 price 的依赖关系、newOrderRespType 的语义、下单后返回/回执行为，以及精度规整的具体规则。对于一个会产生真实交易影响的工具，这些遗漏使 agent 在行动后无法准确预测结果。

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 描述覆盖率 0%，描述承担了很大责任，且确实对 dryRun、reduceOnly、positionSide、timeInForce、goodTillDate 等约 5-6 个参数补充了语义。但 price 与 LIMIT 的关系、quantity 的含义、newClientOrderId、newOrderRespType(ACK/RESULT) 等重要参数的语义仍完全未解释，仅凭枚举值无法让 agent 正确选择。

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?

描述明确以「下单（自动精度规整）」开头，给出了具体动作+资源，并且用「自动精度规整」点出了该工具的一个独特行为特征。标题和名称本身已清楚表明这是下单工具，但描述没有显式说明它与 trading_place_algo、trading_modify_order 等兄弟工具的边界，因此扣一分。

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

Usage Guidelines4/5

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

描述给出了多条明确的调用条件：dryRun=true 时仅校验不提交、reduceOnly 仅单向模式可用、timeInForce=GTD 时必须提供 goodTillDate、双向模式必须传 positionSide，并指明可用 trading_position_mode 查询持仓模式。这些是清晰、可执行的上下文，但没有显式说明何时不应使用本工具而应改用其他兄弟工具（如 algo 下单），故为4分而非5分。

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

Deploy Server

下单

Instructions

Tool call template

Input Schema

Schema Changelog

TDQS

Other Tools