amazing-binance-mcp

Overview Schema Source Related Servers Discussions Admin

binance_get_spot_account

Read-onlyIdempotent

Retrieve spot account balances, trading permissions, and commission rates to monitor account state and verify whether trading, withdrawals, and deposits are allowed.

Instructions

Get spot account state: trade/withdraw/deposit flags, commission rates, balances.

Calls GET /api/v3/account (SIGNED, USER_DATA). IP weight 20 per call.

When to Use:

To check current spot balances (free + locked) for one or all assets.
To confirm whether the account can currently trade, withdraw, or deposit, and what its maker/taker/buyer/seller commission rates are.

When NOT to Use:

For a specific symbol's commission (with any special/discount overrides) — use binance_get_commission_rates.
For non-spot wallets (Funding, Earn, ...) — use the wallet-account tools.

Returns: A markdown block (or JSON with response_format="json") with canTrade/ canWithdraw/canDeposit, account type, commissionRates (maker/taker/buyer/ seller via fmt_num), permissions, last update time, and the balances list (free/locked via fmt_num). When omit_zero_balances is True (the default) and no asset filter is given, a count of hidden zero-balance assets is shown. Display is capped at MAX_DISPLAY_ROWS (50) with a truncation note; JSON mode instead adds truncated/balancesShown/balancesMatched fields so truncation is machine-readable too.

Examples: params = {} params = {"omit_zero_balances": False} params = {"asset": "USDT"}

Error Handling: -2015 means the key lacks Reading permission or this machine's IP is not on the key's allowlist. An empty balances list after filtering means the asset filter matched nothing, or every balance was zero and got hidden.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds substantial value beyond these: rate limit (IP weight 20), error code 2015 meaning, truncation behavior, and how omit_zero_balances affects output. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but tightly structured with clear headers (purpose, when to use/not, returns, examples, errors). Every sentence contributes functional information—rate limits, defaults, edge cases—and the purpose is front-loaded. No redundancy.

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?

For a complex account-state tool, the description covers purpose, usage boundaries, output format details (including truncation and JSON fields), parameter effects, examples, and error interpretation. With an output schema present, the return-value explanation is bonus but not redundant. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already provides descriptions for asset, response_format, and omit_zero_balances, the description enriches these by explaining their effects on output (e.g., asset filter overriding omit_zero_balances, truncation notes, JSON fields). It also shows concrete parameter examples. This fully compensates for the schema coverage signal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise statement of what the tool does: get spot account state including trade/withdraw/deposit flags, commission rates, and balances, backed by the specific API endpoint. It explicitly contrasts with sibling tools (binance_get_commission_rates and wallet-account tools), making the tool's scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Dedicated 'When to Use' and 'When NOT to Use' sections give concrete use cases (check balances, confirm account flags/commissions) and name the exact alternatives for excluded scenarios. This is explicit routing guidance with no reliance on inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server