Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_custodian_transfer_history

Retrieve custodial partner transfer history, including ExpressTrade and Undo transfers, with status, amounts, and timestamps. Filter by rail, asset, time range, transfer ID, or client order ID.

Instructions

Get history of transfers from custodial partner, including ExpressTrade and Undo transfers.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Returns transfer history with status, amounts, and timestamps.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
railYesCustodial partner identifier (all uppercase)
assetNoFilter by asset (e.g., BTC)
limitNoResults per page (default: 20, max: 100)
endTimeNoEnd time in milliseconds
startTimeNoStart time in milliseconds
transferIdNoFilter by specific transfer ID
clientOrderIdNoFilter by your reference ID
expressTradeTransferNoFilter by ExpressTrade transfers only

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

B3.2/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 usefully discloses the auth requirement (custodial API key) and the shape of the returned records (status, amounts, timestamps). It omits read-only confirmation, pagination behavior, and rate limits, which the schema's page/limit fields hint at but the description never explains.

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?

Two short paragraphs with the auth warning front-loaded before the return-value summary; zero filler. The sentence could be tightened further but nothing is wasted.

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 read-only history tool with a fully documented schema and no output schema, the definition covers purpose, credential requirement, and the general return payload. The main missing piece is differentiation from the numerous sibling transfer-history endpoints.

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 (rail, page, limit, time range, transferId, clientOrderId, expressTradeTransfer) is already documented in the schema. The description adds only a vague nod to the ExpressTrade filter and nothing about the required 'rail' identifier's format.

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 history of transfers from custodial partner') and even names the transfer subtypes included (ExpressTrade, Undo). It does not, however, distinguish itself from the many sibling history tools (wallet_transfer_history, settlement_history, cl_transfer_history), so an agent must infer the split from the name 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?

The only guidance is a prerequisite warning that a Custodial Solution API key is required. There is no statement of when to choose this tool over the wallet-transfer, settlement, or CL/US transfer history siblings, and no exclusions or conditions.

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