Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_balance

Retrieve Binance.US exchange wallet and custodial sub-account balances for institutional custody partners; requires a custodial solution API key, not a standard key.

Instructions

Get balance information for Binance.US exchange wallet and custodial sub-account.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY - Standard API keys will not work.

This endpoint is for institutional custody partners (e.g., Anchorage, BitGo).

Response includes:

  • exchangeWalletBalance: Balances in your Binance.US exchange wallet

  • custodialAcctBalance: Balances in your custodial sub-account

Each balance entry contains:

  • asset: Asset symbol

  • free: Available balance

  • locked: Locked balance

  • inSettlement: Amount in settlement (custodial only)

  • lastUpdatedTime: Last update timestamp

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": {
      "rail": "<rail>"
    },
    "name": "binance_us_cust_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.

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

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

With no annotations supplied, the description carries the full burden and does meaningful work: it warns loudly that a custodial solution API key is required and that standard keys fail, and it names the institutional partners the endpoint serves. It stops short of disclosing rate limits, read-only semantics, or error behavior.

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?

The auth warning is front-loaded and visually separated, and the response fields are enumerated in a scannable list. The per-entry field breakdown is slightly long but earns its place because there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read endpoint with no output schema, the description supplies the essential return shape (exchangeWalletBalance, custodialAcctBalance, asset/free/locked/inSettlement) and the auth constraint, so an agent can call it correctly. What is missing is the relationship to the sibling balance endpoints and any indication of what happens when the rail is wrong or unsupported.

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% and the single 'rail' parameter is fully documented in-schema (uppercase custodial partner name, e.g., ANCHORAGE, BITGO), so baseline 3 applies. The description adds no meaning about the parameter itself, only about response contents.

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 balance information for Binance.US exchange wallet and custodial sub-account') and scopes it to both wallet types. It does not, however, distinguish itself from close siblings like binance_us_cust_available_balance or binance_us_custodial_balance, which an agent must choose between.

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?

The description clearly signals the audience ('institutional custody partners') and the key prerequisite (custodial solution API key required, standard keys will not work), which is strong gating context. It gives no explicit guidance on when to pick this over the sibling balance endpoints, so usage is only implied by the field list.

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