Retrieves portfolio margin account balances from Binance, returning all assets or a single asset balance when a symbol is specified.
Query portfolio margin account balance.
| Name | Required | Description | Default |
|---|---|---|---|
| asset | No | Asset symbol (e.g., BTC, USDT). If not provided, returns all assets | |
| recvWindow | No | The value cannot be greater than 60000 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'Query' implies a read-only operation, but the description does not mention authentication requirements, rate limits, what the balance includes (assets, liabilities, cross-margin status), or any other behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. For a simple query tool, this is appropriately sized and direct.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity and full schema coverage, the description is minimally adequate for selection. However, with no output schema and no annotations, it leaves open what the returned balance represents and lacks any behavioral context that would help an agent call it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already documents both parameters, including the asset fallback behavior. The description adds no parameter meaning beyond the schema, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Query') and resource ('portfolio margin account balance'), making the tool's purpose clear. It does not explicitly distinguish itself from sibling tools like BinancePortfolioMarginGetAccount or BinanceWalletQueryUserWalletBalance, but the resource is specific enough for an agent to distinguish.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use guidance, no mention of alternatives, and no exclusions. The implied usage is simply querying a portfolio margin balance, but an agent gets no help deciding between this and similar balance or account-info endpoints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.