amazing-binance-mcp

by trustxai

Overview Schema Source Related Servers Discussions Admin

Python

Local

binance_get_user_assets

Read-onlyIdempotent

List non-zero Spot wallet balances and optionally value them in BTC, giving a compact snapshot of your actual holdings.

Instructions

List the Spot wallet's non-zero balances, optionally valued in BTC.

Calls POST /sapi/v3/asset/getUserAsset (SIGNED, IP weight 5). Another Binance query that uses POST; it is on the client's read allowlist and works with the trading kill-switch off. With no asset filter it returns every asset with a positive balance — unlike /api/v3/account, zero balances are omitted by Binance itself.

When to Use:

For a compact "what do I actually hold on Spot" answer, with a BTC valuation.
As the asset seed for binance_discover_traded_symbols (trade_history.py).

When NOT to Use:

For the full account view (permissions, commission rates, canTrade) — use binance_get_spot_account (spot_account.py).
For the Funding wallet — use binance_get_funding_wallet.

Returns: A markdown table of asset / free / locked / freeze / withdrawing / ipoable (plus BTC valuation and a total when need_btc_valuation is set), capped at 50 rows, or the raw Binance array with response_format="json".

Examples: params = {} params = {"asset": "BTC", "need_btc_valuation": True}

Error Handling: -2015 means the key lacks Reading permission or this IP is not allowlisted. A 404 means the base URL has no /sapi (the spot testnet).

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, openWorldHint, idempotentHint, and non-destructive. The description adds substantial behavioral context: the exact endpoint and method (POST /sapi/v3/asset/getUserAsset), IP weight, that it works with the trading kill-switch off, that Binance omits zero balances, a 50-row cap, response format options, and error codes. This goes far beyond what annotations provide.

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?

Although long, the description is tightly structured with clear sections: summary, endpoint info, When to Use, When NOT to Use, Returns, Examples, and Error Handling. It front-loads the core purpose and avoids redundancy. Every sentence adds distinct value, and the length is justified by the tool's complexity.

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?

The description covers all aspects an agent needs: purpose, usage context, differentiation from siblings, parameter semantics, return format, example calls, and error handling. Even though an output schema exists, the description explains the return structure (markdown table with specific columns) and raw JSON fallback, making it self-sufficient for correct invocation.

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?

The description explains each parameter's effect: asset filtering (with the default behavior of returning all positive balances), need_btc_valuation for BTC valuation, and response_format for markdown vs raw JSON. It provides concrete examples of parameter usage, adding meaning that the schema alone does not convey, especially given the schema's terse descriptions.

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: 'List the Spot wallet's non-zero balances, optionally valued in BTC.' It specifies the resource (Spot wallet), the verb (list), and the scope (non-zero balances). It explicitly differentiates from the full account endpoint and names sibling tools to avoid confusion.

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?

The 'When to Use' and 'When NOT to Use' sections are explicit, naming binance_get_spot_account and binance_get_funding_wallet as alternatives with the exact conditions that select them. It also notes the API's behavior (omits zero balances) that distinguishes it from /api/v3/account, giving clear routing guidance.

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

Deploy Server