撤销全部未成交
trading_cancel_allCancel all open orders for a specified trading symbol on Binance Futures. Clears unfilled orders to manage risk and free up margin.
Instructions
撤销指定交易对全部未成交订单。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
trading_cancel_allCancel all open orders for a specified trading symbol on Binance Futures. Clears unfilled orders to manage risk and free up margin.
撤销指定交易对全部未成交订单。
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v3.0.1Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / symbol / descriptionRemoved value: -"交易对符号 如 BTCUSDT"v2.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations 已声明 destructiveHint=true、readOnlyHint=false,而描述进一步明确了破坏范围为“指定交易对的全部未成交订单”,补充了操作规模和对象。描述与 annotations 一致,无矛盾。
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
整个描述只有一句简短完整的中文,信息密度高,没有冗余内容,也没有重复schema已经能直接看到的内容之外的无用信息。
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
作为销毁性操作,描述说明了取消范围和对象,但缺少 symbol 格式约束、取消后的返回行为,以及是否对已提交未成交的算法订单生效等上下文。由于没有输出 schema,描述本身并未完整覆盖调用者可能需要的全部行为信息。
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
输入 schema 只有一个 symbol 参数且无任何说明,schema 描述覆盖率为 0%。描述中的“指定交易对”为 symbol 参数提供了基础语义,但未说明 symbol 的具体数值格式(如 BTCUSDT 还是 BTC/USDT),也没有给出示例,因此补偿有限。
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
描述包含明确动词“撤销”、目标资源“全部未成交订单”以及作用范围“指定交易对”,清晰说明工具功能。它与同组工具 trading_cancel_order(撤销单个订单)和 trading_cancel_algo(撤销算法订单)在语义上可区分。
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
描述隐含了使用场景:需要撤销某个交易对的全部未成交订单时使用。但没有明确说明在单笔撤单时应改用 trading_cancel_order,也没有给出任何“何时不要使用”或替代工具的排除说明,属于隐含而非显式指导。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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