Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cancel_order

Cancel an active Binance.US order using an order ID or original client order ID to stop an unwanted trade. Provide the trading pair symbol and the order identifier.

Instructions

Cancel an active order on Binance.US. Either orderId or origClientOrderId must be provided.

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": "binance_us_cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTrading pair symbol (e.g., BTCUSD)
orderIdNoThe order ID to cancel
recvWindowNoReceive window in milliseconds (max 60000)
newClientOrderIdNoNew client order ID for this cancel request
origClientOrderIdNoThe original client order ID to cancel
cancelRestrictionsNoCancel restrictions: ONLY_NEW or ONLY_PARTIALLY_FILLED

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether cancellation is irreversible, what permissions or authentication are required, what happens if the order is already filled or missing, or what the response contains.

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?

The description is two sentences with no wasted wording. The core action is front-loaded, and the required identifier condition follows immediately.

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?

The tool has six parameters and no annotations, but schema coverage is complete and the crucial identifier requirement is documented. Completeness is still limited by the absence of guidance on sibling alternatives and mutation risks, which matter for a cancellation endpoint.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents each parameter. The description adds a meaningful constraint beyond the schema by stating that either orderId or origClientOrderId must be provided for the request.

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 states a specific verb and resource: cancel an active order on Binance.US. It is clear what the tool does, but it does not explicitly differentiate it from siblings such as cancel_all_open_orders, cancel_oco, or the custody cancel variants.

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?

It gives an important invocation constraint: either orderId or origClientOrderId must be provided. It does not explain when to use this tool rather than cancel_all_open_orders, cancel_oco, or other cancellation alternatives.

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