Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_wallet_transfer_history

Retrieve the history of transfers from your Binance.US exchange wallet to a custodial sub-account, including status, amounts, and timestamps; filter by rail, asset, or time range.

Instructions

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

⚠️ 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_wallet_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 (default: now)
startTimeNoStart time in milliseconds (default: 90 days ago)
transferIdNoFilter by specific transfer ID
clientOrderIdNoFilter by your reference ID

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

A3.5/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It usefully discloses the auth requirement (Custodial Solution API key) and the return payload shape (status, amounts, timestamps), but says nothing about pagination limits, rate limits, or the default 90-day window that shapes results.

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 blocks: the purpose sentence first, then the auth warning and return summary. The warning is front-loaded and visually separated, and no sentence is redundant. Slightly clipped, but nothing 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 read-only history endpoint with full schema coverage but no annotations and no output schema, the description covers purpose, authentication gate, and the shape of returned records. Remaining gaps (pagination semantics, rate limits) are modest for a filtered list tool.

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 eight parameters including the required uppercase 'rail' identifier, time bounds, and ID filters are already documented. The description adds no parameter-level meaning beyond the schema, which is the expected baseline here.

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 a clear directionality: 'history of transfers from Binance.US exchange wallet to custodial sub-account'. That directional detail distinguishes it from sibling read tools such as the custodian-side transfer history, though it never names a sibling explicitly.

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 usage implication is clear (call this to inspect past custodial wallet transfers) and it flags the hard prerequisite of a Custodial Solution API key. It offers no explicit when-to-use vs. when-not guidance and does not route the agent to the transfer-creation or custodian-history siblings.

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