Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_cancel_orders_symbol

Cancels all active custodial orders for a specified trading pair, including OCO orders, and returns the canceled orders. Requires a custodial solution API key.

Instructions

Cancel all active custodial orders for a specific trading pair.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

This includes OCO orders. Use with caution.

Response is an array of all canceled orders.

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_orders_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
symbolYesTrading pair to cancel all orders for (e.g., BTCUSD)

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

A3.7/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does reasonably well: it discloses the auth requirement (custodial solution API key), the destructive scope (all active orders, including OCO), a caution signal, and the return shape (array of canceled orders). It omits whether cancellation is recoverable and any per-rail caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Four short lines, front-loaded with the action and immediately followed by the auth warning and the OCO caveat. Nothing is padded, though the caution line and the auth warning could be merged without loss.

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 destructive two-parameter mutation with no annotations and no output schema, the description covers the key prerequisites, the destructive scope, and the return type. Missing only error/empty-state behavior and any mention of rate limits or confirmation semantics.

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 coverage is 100%, with both 'rail' and 'symbol' fully documented in the schema, so the baseline of 3 applies. The description reinforces the trading-pair scoping but adds no format or constraint detail 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?

The description gives a specific verb and resource ('Cancel all active custodial orders') plus a clear scope ('for a specific trading pair') and notes that OCO orders are included, which implicitly separates it from the single-order and OCO-only cancel siblings. It stops short of naming an alternative tool, so the differentiation is inferred rather than explicit.

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?

'Use with caution' and the custodial-key prerequisite signal this is a bulk destructive operation, giving implied guidance. However, it never states when an agent should prefer this over binance_us_cust_cancel_order or binance_us_cust_cancel_oco, nor what happens if no orders are open.

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