Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_withdraw_crypto

Submit a crypto withdrawal request from your Binance.US account by specifying coin, network, address, and amount; verify the destination address carefully before transferring funds.

Instructions

Submit a crypto withdrawal request. Requires withdrawal permission on API key. ⚠️ This action transfers funds OUT of your account - verify address carefully!

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": {
      "coin": "<coin>",
      "network": "<network>",
      "address": "<address>",
      "amount": "<amount>"
    },
    "name": "binance_us_withdraw_crypto"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesAsset symbol, e.g., BTC, ETH, USDT
amountYesWithdrawal amount
addressYesWithdrawal destination address
networkYesWithdrawal network, e.g., ERC20, BEP20, BTC. Ensure address type matches network!
addressTagNoMemo/tag for coins like XRP, XMR, etc.
recvWindowNoThe value cannot be greater than 60000
withdrawOrderIdNoClient ID for the withdrawal (for your reference)

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.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that funds leave the account and that withdrawal permission is required. However, it omits important financial-mutation behavior such as irreversibility, fees, processing delays, limits, or what happens after submission, leaving meaningful gaps for a high-risk operation.

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

Conciseness5/5

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

The description is two short sentences and front-loads the core action before the permission requirement and warning. Every sentence adds useful information with no wasted wording.

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 financial mutation with no annotations and no output schema, the description covers the essential permission and safety warning but does not explain return behavior, fees, or processing details. It is adequate for selecting the tool but not complete for fully understanding the 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 description coverage is 100%, so parameter meanings are already documented in the input schema. The description does not add any parameter-specific semantics beyond the schema, which is acceptable at baseline but not enhanced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: "Submit a crypto withdrawal request." It clearly identifies the operation as crypto withdrawal, which distinguishes it from the fiat withdrawal sibling by name and function.

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?

It gives a clear prerequisite—withdrawal permission on the API key—and a strong operational warning to verify the address carefully. It does not explicitly state when to use this versus the fiat withdrawal sibling, so it falls short of full alternative-routing guidance.

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