Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_order_history

Retrieve historical custodial trade orders for a custodial partner, with optional filters by symbol, time range, and order ID to review status and execution details.

Instructions

Get historical custodial trade orders.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

If symbol is not sent, orders for all symbols will be returned.

Response is an array of orders with full details including status, executedQty, and expressTradeFlag.

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

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
limitNoMax records (default: 200)
fromIdNoStart from this order ID
symbolNoTrading pair (e.g., BTCUSD). If omitted, returns all symbols.
endTimeNoEnd timestamp in milliseconds
startTimeNoStart timestamp in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it flags the custodial API key requirement prominently, discloses the all-symbols default, and pre-announces the response shape (array of orders with status, executedQty, expressTradeFlag). It stops short of mentioning rate limits or how limit/fromId pagination interacts with time-range filtering.

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?

Four short, front-loaded blocks: purpose, auth warning, default scoping, and return shape. Nothing is redundant and the most consequential constraint (custodial key) is surfaced immediately after the purpose line.

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 six-parameter read tool with no output schema and no annotations, the definition covers the essentials: purpose, credential requirement, default scoping, and return contents. It is thin on pagination semantics (limit default 200, fromId interplay) and on how time windows are applied, which would matter for large result sets.

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 all six parameters including rail, limit, fromId, and time bounds are already documented in structured data. The description only restates the symbol-omitted default, which the schema also states, adding no new parameter meaning.

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 ("Get historical custodial trade orders"), which is unambiguous about what is returned. It does not differentiate from nearby siblings such as binance_us_cust_trade_history or binance_us_cust_get_order, so an agent must infer the distinction from names alone.

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?

There is no explicit when-to-use guidance and no named alternative for the trade-history vs. order-history decision. The only scoping help is the incidental note that omitting symbol returns all symbols, which is a default behavior rather than usage guidance.

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