Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_transfer_history

Retrieve transfer history from custodial partners to Binance.US custodial sub-accounts, including ExpressTrade, Custodian, and Undo transfers.

Instructions

Get history of transfers from custodial partner to Binance.US custodial sub-account.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Includes ExpressTrade transfers, Custodian transfers, and Undo transfers.

Response includes:

  • data: Array of transfer records

  • total: Total number of transfers

Each record contains: transferId, clientOrderId, asset, amount, status, expressTrade flag, createTime, updateTime

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
assetNoFilter by asset (e.g., BTC)
limitNoRecords per page (default: 20, max: 100)
endTimeNoEnd timestamp (default: now)
startTimeNoStart timestamp (default: 90 days ago)
transferIdNoFilter by specific transfer ID
clientOrderIdNoFilter by client order ID
expressTradeTransferNoFilter ExpressTrade transfers only

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the auth requirement, enumerates the transfer categories covered (ExpressTrade, Custodian, Undo), and describes the response envelope. It omits rate limits and default time-window behavior, which the schema only partially covers.

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 scoping sentence is front-loaded, the auth warning is isolated for visibility, and the response section is justified because no output schema exists. No sentence is redundant.

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 9-parameter history tool with no annotations and no output schema, the description supplies both the prerequisite and the return structure, which is most of what an agent needs. Remaining gaps are pagination semantics and filter-combination behavior across the nine parameters.

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; the description adds marginal value by explaining that ExpressTrade, Custodian, and Undo transfers are all included, which gives context for the expressTradeTransfer filter flag. It does not clarify the relationship between the time-range and transferId/clientOrderId filters or how they combine.

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 with scope: 'Get history of transfers from custodial partner to Binance.US custodial sub-account'. The direction of the transfer implicitly separates it from wallet-transfer and subaccount-transfer siblings, but no sibling is named explicitly, so it stops short of a 5.

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 'REQUIRES CUSTODIAL SOLUTION API KEY' warning is a genuine prerequisite that prevents wasted calls, and the enumeration of transfer types implies the scope of history returned. However, it never says when to use this instead of the closely named transfer-history siblings, leaving that inference to the agent.

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