Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_wallet_transfer_history

Retrieve transfer history from a Binance.US exchange wallet to a custodial sub-account. Filter records by rail, asset, transfer ID, client order ID, or time range to track transfer status.

Instructions

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

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Response includes:

  • data: Array of transfer records

  • total: Total number of transfers

Each transfer record contains: transferId, clientOrderId, asset, amount, status, 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_wallet_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

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

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description has to carry the behavioral burden, and it does disclose the custodial-solution API key requirement plus the response envelope ('data' array and 'total'). It says nothing about pagination traversal, default time window behavior when startTime is omitted, or error conditions, which are relevant for a filtered history endpoint.

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?

The description is front-loaded with the action, then the access warning, then the return shape — a sensible ordering. The record field enumeration is somewhat list-like, but since no output schema exists it earns its place; only the blank-line formatting is slightly loose.

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 an 8-parameter, read-only history tool with no annotations and no output schema, the definition covers the essential gaps: authentication tier and returned record structure. The remaining omissions (pagination semantics, described defaults for the time window) are modest because the schema documents each parameter thoroughly.

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%, with page, rail, asset, limit, startTime, endTime, transferId, and clientOrderId all documented inline, so the baseline is 3. The description adds no parameter-level meaning beyond what the schema already states — it does not, for example, explain the default 90-day window or how transferId/clientOrderId filters interact with the time range.

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 uses a specific verb and resource ('Get history of transfers') and adds directional scope ('from Binance.US exchange wallet to custodial sub-account'), which meaningfully separates it from the many sibling transfer-history tools. It does not explicitly name any sibling, so an agent must infer the distinction from the direction wording 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 usage guidance is the prerequisite warning 'REQUIRES CUSTODIAL SOLUTION API KEY', which is useful but is an access constraint rather than a when-to-use rule. Given seven-plus sibling transfer-history tools (custodial_wallet_transfer_history, cust_transfer_history, cl_transfer_history, subaccount_transfer_history), no condition is given for choosing this one over them.

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