Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_subaccount_transfer

Transfer assets between a Binance.US master account and sub-accounts by specifying sender and recipient emails, asset symbol, and amount.

Instructions

Execute an asset transfer between master account and a sub-account. ⚠️ This moves funds between accounts!

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": {
      "fromEmail": "<fromEmail>",
      "toEmail": "<toEmail>",
      "asset": "<asset>",
      "amount": "<amount>"
    },
    "name": "binance_us_subaccount_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset symbol to transfer, e.g., BTC, ETH
amountYesAmount to transfer
toEmailYesRecipient email address
fromEmailYesSender email address
recvWindowNoThe value cannot be greater than 60000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / fromEmail / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • addedInput schema / properties / toEmail / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that funds are moved between accounts, which is the critical trait, but says nothing about reversibility, whether the transfer is atomic, required API key permissions, rate limits, or what the response returns.

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 sentences with the core action front-loaded. The warning sentence is somewhat redundant with the first sentence's 'transfer' verb, but it earns its place as a safety flag on a fund-moving operation.

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

Completeness2/5

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

For a 5-parameter, no-annotation, no-output-schema mutation that moves real funds, the definition is thin. It omits the direction semantics of the email parameters, permission prerequisites, and any note on the response, leaving the agent to call a destructive financial operation with only schema-level knowledge.

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 every parameter including recvWindow is already documented in the schema. The description adds no meaning beyond that — notably it does not explain that fromEmail/toEmail must identify the master and sub-account respectively, which is the one ambiguity the schema leaves open.

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: 'Execute an asset transfer between master account and a sub-account.' This clearly separates it from history/assets/list siblings. It does not, however, distinguish it from the other transfer-style siblings (cl_transfer, cust_transfer, custodial_wallet_transfer), so an agent must infer the account-type scoping from the tool name alone.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many other transfer tools, and no stated prerequisites (e.g., sub-account transfer permissions enabled, fromEmail must be the master account). The only usage signal is the warning that funds move, which is a caution rather than a selection rule.

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