Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_deposit_history

Retrieves crypto deposit history from Binance.US, letting you filter by coin, status, and time range to track incoming deposits.

Instructions

Get crypto deposit 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_deposit_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoFilter by coin symbol
limitNoNumber of results. Default: 1000, Max: 1000
offsetNoPagination offset. Default: 0
statusNoStatus filter: 0=pending, 1=success, 6=credited but cannot withdraw
endTimeNoEnd time in ms. Default: now
startTimeNoStart time in ms. Default: 90 days ago
recvWindowNoThe value cannot be greater than 60000

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 supplied, the description carries the full burden. It discloses that this is a read ('Get ... history') and which dimensions are filterable, but says nothing about authentication needs, rate limits, result ordering, or the 90-day default window that materially affects what gets returned.

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, front-loaded with the purpose before the filtering note. There is no filler, though the second sentence largely duplicates parameters the schema already explains.

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 7-parameter history endpoint with no output schema, the definition stops at purpose and filters. It never characterizes the returned records (transaction id, address, amount, status, timestamps), which an agent must know to use the results 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 the baseline of 3 applies. The description only restates the coin, status, and time-range filters already documented in the schema and adds no interpretation beyond it.

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: 'Get crypto deposit history'. The resource is unambiguous and separable from siblings such as withdraw_history or deposit_address, though the description never explicitly contrasts itself with those siblings.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites such as API key permissions, and no named alternative. The only implicit guidance is that results can be narrowed by coin, status, or time range.

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