Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_withdraw_history

Retrieve crypto withdrawal history with filters for coin, status, time range, pagination, and client withdrawal ID to audit or reconcile account activity.

Instructions

Get crypto withdrawal history. Filter by coin, status, or time range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "binance_us_withdraw_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoFilter by coin symbol
limitNoNumber of results. Default: 1000, Max: 1000
offsetNoPagination offset. Default: 0
statusNoStatus filter: 0=email sent, 1=canceled, 2=awaiting approval, 3=rejected, 4=processing, 5=failure, 6=completed
endTimeNoEnd time in ms. Default: now
startTimeNoStart time in ms. Default: 90 days ago
recvWindowNoThe value cannot be greater than 60000
withdrawOrderIdNoFilter by client withdrawal ID

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?

No annotations are provided, so the description carries the full disclosure burden. It makes clear this is a read-style history query, but omits authentication requirements, rate limits, the 90-day default window, the 1000-result cap, and return behavior.

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 with the purpose front-loaded and no wasted wording. Nothing is buried or repeated unnecessarily.

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 an eight-parameter history tool with complete schema descriptions, the definition is minimally adequate. It does not address the absence of an output schema, pagination semantics, or the default time window, which would help an agent call it correctly.

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 eight parameters, including status mappings and defaults, are already documented in the input schema. The description summarizes three filter dimensions but adds no meaning beyond what the schema provides.

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: retrieving crypto withdrawal history. It is distinguishable from withdrawal-mutation siblings by the word "history," though it does not explicitly contrast with sibling history tools such as deposit_history or transfer_history.

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?

Filtering by coin, status, or time range implies the intended usage context for narrowing historical records. However, there is no explicit guidance on when to prefer this tool over related history endpoints or on pagination and default-window behavior.

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