Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_wallet_transfer

Transfer assets from your Binance.US exchange wallet to a custodial sub-account for trading. Requires a Custodial Solution API key and returns transfer status, ID, and reference details.

Instructions

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

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Use this to move assets from your Binance.US exchange wallet to your custodial sub-account for trading.

Response includes:

  • asset: Transferred asset

  • amount: Transfer amount

  • clientOrderId: Your reference ID (or auto-generated)

  • transferId: Unique transfer identifier

  • status: Transfer status (SUCCESS, PENDING, etc.)

  • createTime: Transfer creation timestamp

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

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
assetYesAsset to transfer (e.g., BTC, ETH)
amountYesAmount to transfer
clientOrderIdNoYour unique 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
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the auth requirement (Custodial Solution API key) and enumerates response fields including a status enum hint (SUCCESS, PENDING), which implies asynchronous settlement. It does not discuss irreversibility of moving funds, failure/insufficient-balance behavior, or idempotency of clientOrderId, which matter for a value-moving mutation.

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?

Purpose is front-loaded, followed by the API key warning, then the response shape. Every block is relevant, though listing six response fields in prose is bulkier than necessary given it is already implicit in the tool's operation.

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 mutation tool with no annotations and no output schema, the description compensates by documenting the returned fields and the credential prerequisite. Remaining gaps are behavioral risk details (reversibility, error conditions) rather than missing invocation-critical information.

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 semantics beyond that (e.g., rails available, amount precision/rounding, or how clientOrderId behaves on retries). Baseline 3 is appropriate when the schema does the work.

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 concrete verb and both resources with direction: transfer from the Binance.US exchange wallet to a custodial sub-account. The second sentence reinforces the same action and the 'for trading' end goal. It does not, however, distinguish itself from the many sibling transfer tools (e.g., binance_us_custodial_wallet_transfer), so an agent cannot fully disambiguate from description alone.

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?

Provides an implied use case ('move assets ... for trading') and a hard prerequisite (requires a custodial solution API key). There is no explicit when-not guidance and no named alternative transfer tool to route to, despite a crowded family of transfer 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