Skip to main content
Glama
Sign In
Binance MCP Server

Binance MCP Server

by iuk-ink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

改单

trading_modify_order
Destructive

Modify unfilled limit orders on Binance Futures. Specify orderId or origClientOrderId, then update symbol, side, quantity, or price.

Instructions

修改未成交订单（仅 LIMIT）。orderId 与 origClientOrderId 二选一。

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>",
      "quantity": "<quantity>",
      "price": "<price>"
    },
    "name": "trading_modify_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
priceYes
symbolYes
orderIdNo
quantityYes
origClientOrderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / orderId / description
      Removed value: -"系统订单ID"
    • removedInput schema / properties / origClientOrderId / description
      Removed value: -"自定义订单ID"
    • removedInput schema / properties / price / description
      Removed value: -"新价格"
    • removedInput schema / properties / quantity / description
      Removed value: -"新数量"
    • removedInput schema / properties / side / description
      Removed value: -"方向 BUY=买入 / SELL=卖出"
    • removedInput schema / properties / symbol / description
      Removed value: -"交易对符号 如 BTCUSDT"
    • changedInput schema / required
      Previous value: -[
-  "symbol",
-  "side"
-]New value: +[
+  "symbol",
+  "side",
+  "quantity",
+  "price"
+]
  2. Addedv2.0.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already signal destructive behavior, and the description adds useful constraints: only unfilled orders and only LIMIT type are elligate for modification. It does not disclose deeper behavior such as whether existing order is replaced/caneled or how failures handled, but it meaningfully extends 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.

Conciseness5/5

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

One sentence delivers the essential scope and constraint without filler. The key function and the orderId/origClientOrderId exclusivity are front-loaded, making the definition easy and fast to parse.

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?

For a mutation tool with no output schema and no parameter descriptions, the definition is incomplete. It does not describe what happens after a successful modification, whether it replaces or cancels, possible failures, or how to know which side of the order to adjust. An agent would need substantial inferred knowledge to call it correctly.

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

Parameters2/5

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

The schema description covers 0% of parameters, so the description must compensate. It clarifies that orderId and origClientOrderId are mutually exclusive, but it does not explain the meaning of symbol, side, quantity, or price beyond their raw schema names and constraints. This leaves significant semantics implied.

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 states a specific action ('modify unfilled orders') and an explicit scope restriction ('LIMIT only'). This clearly distinguishes the tool from place/cancel/get sibling tools and tells an agent exactly what resource it affects.

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 when to use the tool by restricting modifications to unfilled LIMIT orders, but it provides no explicit guidance about when to prefer this tool over trading_place_order, trading_cancel_order, or other alternatives. The scope is helpful but limited.

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

Deploy Server

Other Tools