Retrieve daily Binance account snapshots by account type (SPOT, MARGIN, FUTURES) and date range to audit balances, with an optional limit up to 30.
Get daily account snapshot.
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | The account type (e.g., SPOT, MARGIN, FUTURES) | |
| limit | No | Default 7, max 30 | |
| endTime | No | End time in milliseconds | |
| startTime | No | Start time in milliseconds | |
| 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 must disclose behavior. It doesn't mention required permissions, rate limits, response format, or any side effects. The description is purely a simple action statement.
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 short sentence with no unnecessary words, but it is under-specified and adds no value beyond the tool name. It is concise in structure but lacking in substantive content.
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?
The tool has 5 parameters including time range and limit, no output schema, and no annotations. The description does not explain what the snapshot includes, how time/limit interact, or what return value to expect. It is inadequate for correct invocation.
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?
All 5 parameters have schema descriptions, so the baseline is 3. The tool description adds no semantic information beyond the schema, so it remains at the baseline.
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 clearly states the tool retrieves a daily account snapshot, but it merely restates the tool name and doesn't distinguish it from sibling wallet tools like BinanceWalletAccountInfo or BinanceWalletUserAsset. No additional details about what the snapshot contains.
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 guidance on when to use this tool versus other wallet endpoints. No alternatives or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.