Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_wallet_transfer

Transfer assets from your Binance.US exchange wallet to a custodial sub-account for trading or settlement.

Instructions

Transfer assets from your Binance.US exchange wallet to your custodial sub-account.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY ⚠️ This moves funds - verify details carefully!

This transfers from your main Binance.US account to your custodial sub-account, which can then be traded or settled to your custodial 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_wallet_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.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the two highest-value traits: an authentication requirement (custodial solution API key) and that this is a fund-moving operation requiring verification. It stops short of stating reversibility mechanics, whether an undo tool must be used, or failure/rate-limit behavior.

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 opening sentence front-loads purpose and the warnings follow immediately, with no filler. There is mild redundancy: the fourth sentence restates the account-to-sub-account direction already given in sentence one, adding only the downstream-use context.

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 high-stakes, unannotated fund-movement tool with no output schema, the definition covers auth and risk but leaves the agent guessing about the response (transfer ID? status?), whether the transfer is synchronous, and what values `rail` accepts. Those are material gaps for an irreversible operation.

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 coverage is 100%, so all four parameters including `rail`, `asset`, `amount`, and `clientOrderId` are already documented in structured data. The description adds nothing about valid `rail` identifiers or how to discover supported assets, so it neither compensates nor extends the schema.

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 a specific direction of movement: 'Transfer assets from your Binance.US exchange wallet to your custodial sub-account.' The directionality distinguishes it from the custodian-transfer and undo-transfer siblings without naming them, but no sibling is called out explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear preconditions ('REQUIRES CUSTODIAL SOLUTION API KEY') and situates the tool in a workflow ('which can then be traded or settled to your custodial partner'), which tells an agent when this step is appropriate. It offers no explicit exclusions or named alternatives such as the transfer-history or undo-transfer tools.

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