Retrieve historical Binance dust transfer records with optional start and end time filters to track when small asset balances were converted.
Get dust log (history of dust transfers).
| Name | Required | Description | Default |
|---|---|---|---|
| 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?
With no annotations, the description carries full burden for behavioral disclosure. It implies a read-only operation, but does not state whether authentication is needed, how results are paginated, or any constraints like time range defaults.
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 clear sentence with a helpful parenthetical clarification. Every word earns its place with no redundancy.
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 is simple, but with no output schema and no annotations, the description is minimal. It explains what the tool returns at a high level but lacks details on return format, pagination, or default time window, leaving gaps for an agent to discover.
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 coverage is 100% for the three optional parameters (startTime, endTime, recvWindow). The description does not add meaning beyond what the schema already provides, so a baseline 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 clearly states the tool retrieves a dust log, defined as history of dust transfers. This distinguishes it from the sibling BinanceWalletDustTransfer which performs the transfer, and from other wallet query tools.
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?
No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, typical use cases (e.g., post-transfer audit), or situations where another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.