kvant-binance-mcp

futures_cancel_order

Cancel a futures order on Binance by providing the trading pair and order ID.

Instructions

Cancel a futures order (requires API key)

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>"
    },
    "name": "futures_cancel_order"
  }
}

Input Schema

Name	Required	Description
`symbol`	Yes	Trading pair
`orderId`	No	Order ID to cancel
`origClientOrderId`	No	Client order ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 4, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. It only mentions API key requirement, but fails to explain that an order identifier (orderId or origClientOrderId) is needed, the nature of cancellation (immediate?), or any return value. This leaves agents uninformed.

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 a single sentence with no wasted words, but it is too brief and underspecified. It lacks structure and important details, making it less helpful than it could be.

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 sparse description, the context is incomplete. It does not clarify how to identify the order (need orderId or origClientOrderId) or what the outcome of cancellation is, which is essential for correct invocation.

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%, so baseline is 3. The description does not add any parameter semantics beyond what the schema already provides, such as explaining the dependency between orderId and origClientOrderId.

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 clearly states 'Cancel a futures order', which is a specific verb-resource pair. It is distinguishable from sibling tools like futures_cancel_all_orders or futures_new_order, though it does not explicitly differentiate.

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_cancel_all_orders. The only hint is 'requires API key', which is trivial and does not help in decision-making.

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