Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_withdraw_fiat

Submit a USD withdrawal request via BITGO to move funds from your Binance.US account to a specified payment account.

Instructions

Submit a USD withdrawal request via BITGO. ⚠️ This action transfers USD OUT of your account!

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": {
      "paymentAccount": "<paymentAccount>",
      "amount": "<amount>"
    },
    "name": "binance_us_withdraw_fiat"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesUSD amount to withdraw
recvWindowNoThe value cannot be greater than 60000
fiatCurrencyNoFiat currency (default: USD)USD
paymentMethodNoPayment method (default: BITGO)BITGO
paymentAccountYesThe account to withdraw funds to

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.2/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. It usefully discloses the most important trait — that USD actually leaves the account — but says nothing about irreversibility, fees, processing time, confirmation requirements, or what happens on failure. That is a meaningful gap for a high-risk financial mutation.

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?

Two short sentences, front-loaded with the action and followed by a high-signal warning. Nothing is wasted and the risk emphasis is placed where it will be read.

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 money-moving operation with no annotations and no output schema, the description should at minimum cover irreversibility, destination prerequisites, and expected confirmation behavior. As written it gives the agent only the bare action and a warning, leaving the operational picture incomplete.

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 all five parameters are already documented in the schema, and the description adds no parameter-level meaning (e.g. that paymentAccount must be a pre-registered/whitelisted destination). Baseline 3 applies 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?

The description states a specific verb and resource ('Submit a USD withdrawal request') and names the payment rail (BITGO), which distinguishes it from the crypto withdrawal sibling. It does not explicitly call out that distinction, so an agent must infer it from 'USD' versus the sibling name.

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 a warning that funds leave the account, but no guidance on when to choose this tool over binance_us_withdraw_crypto or binance_us_withdraw_history, and no prerequisites such as whitelisted accounts or 2FA. Usage is only implied by the tool name and the warning.

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