Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_custodian_transfer

Request your custodial partner to transfer assets to your Binance.US custodial sub-account by specifying rail, asset, and amount; the custody partner executes the transfer.

Instructions

Request asset transfer from a custodial partner account to Binance.US custodial sub-account.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY ⚠️ This initiates a transfer request to your custody partner!

This requests your custodial partner to transfer assets to your Binance.US account. The actual transfer is executed by the custody partner.

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>",
      "asset": "<asset>",
      "amount": "<amount>"
    },
    "name": "binance_us_custodial_custodian_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner identifier (all uppercase)
assetYesAsset to transfer (e.g., BTC, ETH)
amountYesAmount to transfer
clientOrderIdNoYour reference ID (auto-generated if not provided)

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
Behavior4/5

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

With zero annotations the description carries the full burden and does meaningful work: it discloses that this only initiates a request, that the custody partner performs the actual transfer, and that a Custodial Solution API key is required. It stops short of stating whether the call is idempotent, what a response contains, or how to reverse it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key warning is front-loaded, but the body repeats the same idea three times ('Request asset transfer...', 'This requests your custodial partner to transfer assets...', 'The actual transfer is executed by the custody partner'), which dilutes rather than reinforces.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description covers the essential framing (external execution, auth requirement) but omits what the caller gets back, whether clientOrderId provides idempotency, and how to cancel or reverse via the sibling undo 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 rail, asset, amount, and clientOrderId are already documented in the schema. The description adds no extra constraint such as supported rails or asset/rail compatibility, so baseline 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?

The description names a specific verb and resource with directionality: 'Request asset transfer from a custodial partner account to Binance.US custodial sub-account.' That is clear enough to separate it from history/balance siblings, but it never mentions the closely named sibling wallet_transfer or undo_transfer, so the agent must infer which transfer variant is which.

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 description implies the use case (pulling assets in from a custody partner) and states the API-key precondition, but gives no explicit when-to-use/when-not guidance and never points at binance_us_custodial_undo_transfer or wallet_transfer as alternatives.

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