Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_deposit_address

Retrieves a cryptocurrency deposit address, with optional network selection, for receiving funds into a Binance.US account.

Instructions

Get a deposit address for a specific crypto asset. Use this to receive funds into your Binance.US 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": {
      "coin": "<coin>"
    },
    "name": "binance_us_deposit_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin symbol to get deposit address for, e.g., BTC, ETH
networkNoSpecific network to get address for, e.g., ERC20, BEP20
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
Behavior2/5

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

No annotations exist, so the description carries the full burden. It implies a safe read ('get'), but says nothing about whether the returned address is stable or per-call, that the coin and network must be compatible, or that some assets require a memo/tag — all critical for a deposit flow. Only the basic intent is disclosed.

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 action and followed by the purpose. The second sentence is slightly redundant with the tool name but does supply the destination context, so almost nothing is wasted.

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?

With 100% schema coverage and no output schema, the main remaining gap is what the response contains (address, memo/tag, coin/network echo) and the pitfalls of mismatched networks. That omission is meaningful for a funds-routing tool but the core invocation is still fully specified.

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 coverage is 100%, so all three parameters (coin, network, recvWindow) are already documented in the schema, and the description only restates 'for a specific crypto asset'. It adds no meaning about default network behavior or the recvWindow timing tolerance; baseline 3 applies.

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 — 'Get a deposit address for a specific crypto asset' — which is unambiguous about what the call returns. It does not name or distinguish itself from any sibling tool, but the sibling list contains no obvious competing 'deposit address' variant, so confusion risk is low.

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?

'Use this to receive funds into your Binance.US account' gives the intended scenario but no explicit when-not guidance, no pointer to binance_us_deposit_history for verifying incoming deposits, and nothing about needing a matching network. Usage is implied rather than routed.

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