Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_cancel_order

Cancel an active custodial trade order using order ID or original client order ID; returns the canceled order details with CANCELED status.

Instructions

Cancel an active custodial trade order.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Either orderId or origClientOrderId must be provided.

Response includes the canceled order details with status: CANCELED

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": {
      "rail": "<rail>",
      "symbol": "<symbol>"
    },
    "name": "binance_us_cust_cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolYesTrading pair (e.g., BTCUSD)
orderIdNoOrder ID to cancel
newClientOrderIdNoNew client order ID for this cancel operation
origClientOrderIdNoOriginal client order ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / orderId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / orderId / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it discloses the custodial API key prerequisite, the identifier requirement, and the return shape (canceled order details with status CANCELED), which is meaningful for a mutation tool. It does not state what happens on an already-filled or unknown order, whether cancellation is reversible, or any rate-limit behavior, leaving the failure profile undocumented.

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?

Three short lines with the destructive/auth warning front-loaded, then the parameter constraint, then the return value. No filler sentences and nothing that restates the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 annotations and no output schema, the description covers auth, the identifier requirement, and the response contents, which is what an agent needs to call it correctly. It falls short only on error/failure semantics, which are not covered by any structured field.

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 coverage is 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint ('Either orderId or origClientOrderId must be provided') that the flat schema cannot express. It adds nothing about rail casing or newClientOrderId, but the either/or rule is real value beyond the schema.

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?

States a specific verb and resource ('Cancel an active custodial trade order'), and the word 'custodial' plus the API-key warning separate it from the non-custodial binance_us_cancel_order sibling. It does not explicitly distinguish itself from binance_us_cust_cancel_oco or binance_us_cust_cancel_orders_symbol, so routing still requires inference from the singular 'order'.

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?

Usage context is implied by the custodial-key requirement and the constraint that either orderId or origClientOrderId must be supplied, which tells an agent it can only act on custodial accounts and needs one identifier. There is no explicit when-to-use vs. when-not guidance and no sibling alternative is named despite many cancel variants being available.

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