Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_trade_history

Retrieve historical custodial filled trades, including price, quantity, commission, and order details, using a custodial partner rail and API key.

Instructions

Get historical custodial trades (filled orders).

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Returns actual executed trades with price, quantity, and commission details.

Response includes for each trade: symbol, price, qty, quoteQty, time, isBuyer, isMaker, isBestMatch, orderId, commission, commissionAsset

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

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
limitNoMax records (default: 200)
fromIdNoStart from this trade ID
symbolNoTrading pair (e.g., BTCUSD)
endTimeNoEnd timestamp
orderIdNoFilter by order ID
startTimeNoStart timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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
    • addedInput schema / properties / orderId / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / orderId / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It discloses the key authentication constraint and enumerates the returned fields, which is genuinely useful, but says nothing about pagination behavior (limit/fromId interaction), rate limits, or whether results are bounded by a default time window.

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?

Front-loaded with the action and the auth warning first, then the response shape. The middle sentence ('Returns actual executed trades with price, quantity, and commission details') partially duplicates the field list that follows, which is the only wasted content.

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 7-parameter read tool with no output schema, the description covers the essential pieces: auth requirement, semantic meaning of results, and a full field enumeration. The remaining gap is pagination and time-range behavior, which matters for a history endpoint but is not the most critical omission.

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 every parameter is already documented, including the uppercase rail constraint and the default limit of 200. The description adds no further meaning about parameter interaction, such as how fromId paginates against startTime/endTime, so the baseline of 3 applies.

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 — 'Get historical custodial trades (filled orders)' — and clarifies that these are executed fills rather than open/working orders. It does not name the sibling binance_us_cust_order_history to draw the distinction explicitly, so an agent must infer that separation.

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?

The prominent '⚠️ REQUIRES CUSTODIAL SOLUTION API KEY' warning gives a hard prerequisite that filters misuse. However, there is no explicit when-to-use guidance relative to cust_order_history, and no statement of which parameters are required to get meaningful results (only rail is required, but no filtering strategy is suggested).

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