Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_available_balance

Retrieves the available balance in a custodial sub-account for placing new trading orders, filtered by rail and optional asset. Requires a Custodial Solution API key.

Instructions

Get available balance in the custodial sub-account for trading.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Returns the balance available for placing new orders.

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_available_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
assetNoFilter by specific asset

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

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

With no annotations, the description carries the full burden; it does add genuinely useful context, namely the custodial-solution API key requirement and the fact that the returned figure is spendable buying power rather than total holdings. It omits whether the call is read-only (only implied by "Get"), whether locked/in-flight order funds are excluded, and any rate-limit or snapshot-timing 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?

Very short and front-loaded: purpose first, then a high-visibility auth warning. There is mild redundancy between "Get available balance" and "Returns the balance available," which keeps it from a 5.

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 two-parameter, one-required read tool with no output schema, the description covers the essential prerequisites (the custodial key) and the semantic meaning of the return value. The remaining gap — the shape of the balance payload and whether zero balances are returned — is minor given the tool's simplicity.

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%, with the rail parameter already documenting uppercase custodial partner names and asset documenting the filter. The description adds nothing about parameter behavior or defaults, so the 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?

States a specific verb and resource ("Get available balance in the custodial sub-account") and qualifies it as the amount "available for placing new orders," which distinguishes it from a total-balance sibling. It stops short of naming the sibling tools it differs from, so an agent must still infer the boundary against binance_us_cust_balance and binance_us_custodial_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 phrase "for trading" and "available for placing new orders" implies the use case — checking buying power before submitting an order. There is no explicit when-to-use versus when-to-use-an-alternative statement, and no guidance on which balance tool to pick among the similarly named siblings.

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