Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_dust_log

Read-onlyIdempotent

Review past Binance dust-to-BNB conversions, showing each batch's transferred BNB, service charge, and per-asset details. Use it to verify what was swept and confirm service fees.

Instructions

List past dust-to-BNB conversions, with the per-asset detail of each one.

Calls GET /sapi/v1/asset/dribblet (SIGNED, IP weight 1). Binance returns "only the last 100 records" and "only records after 2020/12/01".

When to Use:

  • To find out what a past "convert small balances to BNB" actually converted, and what the service charge was.

  • To check whether an asset disappeared because it was swept as dust.

When NOT to Use:

  • To see what could be converted right now — use binance_get_dust_convertible.

  • To actually convert — that is binance_convert_dust_to_bnb.

Returns: One markdown section per conversion batch (time, transId, total transferred BNB, total service charge) followed by a table of the assets in that batch, or the raw envelope with response_format="json".

Windows: start_time/end_time are optional; Binance caps the history at the last 100 records regardless of the window, and keeps nothing before 2020-12-01.

Examples: params = {} params = {"start_time": "2026-01-01", "end_time": "2026-06-30"}

Error Handling: -2015 means the key lacks Reading permission or this IP is not allowlisted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds substantial behavioral context beyond them: the call is SIGNED with IP weight 1, Binance caps results at the last 100 records regardless of window, no records before 2020/12/01, and error -2015 indicates a permission or allowlist problem. This gives the agent actionable expectations about side effects and failure modes.

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 longer than average, but every section earns its place: purpose, endpoint, usage routing, return format, window caveats, examples, and error handling. It is front-loaded with the core action and uses clear headings so an agent can quickly extract the needed facts.

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 read-only list tool with annotations covering safety and idempotence, the description fully covers what the agent needs: when to use it, what it returns, how parameters behave, Binance's constraints, and the meaning of the main error code. Nothing essential is left to inference.

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 schema already describes start_time, end_time, account_type, and response_format, and the description further clarifies that start_time/end_time are optional, that the 100-record cap overrides any window, and that response_format='json' returns the raw envelope. The examples ('params = {}' and a dated range) show realistic invocation shapes.

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?

Description opens with a specific verb and resource: 'List past dust-to-BNB conversions, with the per-asset detail of each one.' It also names the exact Binance endpoint, so the tool's scope is unambiguous. The 'When NOT to Use' section explicitly distinguishes it from binance_get_dust_convertible and binance_convert_dust_to_bnb.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections that name sibling tools and the conditions that route to them. It also discloses Binance's hard limits (last 100 records, nothing before 2020-12-01), which materially affect when this tool is appropriate.

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

Deploy Server

Other Tools