Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_transfer

Transfer assets from a custodial partner account to your Binance.US custodial sub-account for trading. Requires a custodial solution API key.

Instructions

Transfer assets from custodial partner account to Binance.US custodial sub-account.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Use this to move assets from your custodial partner (e.g., Anchorage) to your Binance.US custodial sub-account for trading.

Response includes:

  • asset: Transferred asset

  • amount: Transfer amount

  • transferId: Unique transfer identifier

  • custodyAccountId/custodyAccountName: Custodian account details

  • status: Transfer status

  • 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_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

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden: it discloses the required API key and the transfer direction, plus the returned fields. But it says nothing about reversibility, idempotency, minimum amounts, failure modes, or whether funds are immediately tradeable versus pending — critical for a money-movement 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 and the auth warning are front-loaded, followed by a compact response-field list with no filler sentences. The bulleted return list is slightly long for a tool with four inputs, but each line is informative given no output schema exists.

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 supplies the credential prerequisite, the transfer direction, and the response shape, which is most of what an agent needs. Missing pieces are the undo path (a binance_us_cust_undo_transfer sibling exists) and any amount or error constraints.

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% and each parameter already documents itself, so the baseline is 3. The description echoes the rail example (Anchorage) but adds no format, casing, or constraint detail beyond what the schema states, including the uppercase rail requirement.

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 direction: transfer assets from a custodial partner account to a Binance.US custodial sub-account. It does not explicitly distinguish itself from near-name siblings such as binance_us_cust_wallet_transfer or binance_us_custodial_custodian_transfer, so an agent must infer the difference from the partner-vs-wallet wording.

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 gives a positive usage context ("move assets from your custodial partner ... for trading") and a prerequisite (custodial solution API key). It names no exclusions and no alternative tool, even though siblings like wallet_transfer and undo_transfer compete for the same intent.

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