Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_balance

Retrieve Binance.US exchange wallet and custodial sub-account balances—including free, locked, and in-settlement amounts—using a custodial solution API key and partner rail.

Instructions

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

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

Returns two balance arrays:

  • exchangeWalletBalance: Balances in your Binance.US exchange wallet

  • custodialAcctBalance: Balances in your Binance.US custodial sub-account

Each balance includes:

  • asset: Asset symbol (e.g., BTC, ETH)

  • free: Available balance

  • locked: Locked balance (in orders, etc.)

  • inSettlement: Amount in settlement process (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_custodial_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner identifier (all uppercase, e.g., 'FIREBLOCKS')

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

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

No annotations are supplied, so the description carries the full burden and does well: it discloses the credential prerequisite and the fact that results are split into two arrays. It does not mention rate limits, pagination, or whether the call is read-only in effect, which are minor remaining gaps for a balance lookup.

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 purpose is front-loaded, the auth warning is prominent, and the bulleted field breakdown is scannable. The per-field listing is slightly verbose for a read-only lookup, but it substitutes for the absent output schema, so most of it earns its place.

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

Completeness5/5

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

With no output schema and no annotations, the description compensates by enumerating both return arrays and every balance field, including the custodial-only 'inSettlement'. An agent knows what it will receive and what credential it needs before calling.

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% and the single 'rail' parameter is fully documented in the schema, so the baseline of 3 applies. The description never mentions 'rail' or the custodial partner identifier, adding no meaning beyond the structured field.

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 first sentence states a specific verb and resource ('Get balance information') and scopes it to the Binance.US exchange wallet and custodial sub-account. It is clear enough to act on, but it never distinguishes itself from closely named siblings such as binance_us_cust_balance or binance_us_cust_available_balance.

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 gives one hard precondition ('REQUIRES CUSTODIAL SOLUTION API KEY - Regular API keys will not work'), which is genuinely useful routing information. However, it offers no when-to-use guidance relative to the other custodial balance tools and no exclusions, so the agent must infer selection from the tool name alone.

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