Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_convert_asset_info

Read-onlyIdempotent

Check the decimal precision Binance Convert accepts per asset, so you can round amounts correctly and avoid -1111 precision errors before requesting a quote.

Instructions

Show the decimal precision (fraction) Convert accepts for each asset.

Calls GET /sapi/v1/convert/assetInfo (SIGNED, IP weight 100). fraction is the number of decimal places an amount may carry for that asset on the convert rail — sending more precision than this is what -1111 rejects.

When to Use:

  • Before binance_get_convert_quote, to round from_amount/to_amount correctly.

  • When a quote was rejected for precision.

When NOT to Use:

  • To find which pairs exist or their min/max sizes — that is binance_get_convert_pairs.

Returns: One row per asset: asset and its accepted decimal places, filtered client-side when asset is given. Markdown display is capped at 100 rows.

Examples: params = {} params = {"asset": "BTC"}

Error Handling: -2015 means the key lacks permission or this machine's IP is not on the key's allowlist; the spot testnet has no /sapi endpoints at all (404).

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

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds valuable behavior beyond that: SIGNED endpoint, IP weight, client-side filtering, 100-row Markdown cap, the -1111 precision error, -2015 permission/IP errors, and testnet 404. No contradiction with annotations.

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?

Well-structured with clear sections, front-loaded purpose, and only functional details: endpoint, usage, examples, and error handling. Every sentence adds value or routes the agent away from mistakes.

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?

Covers endpoint, authentication/signing, rate weight, precision behavior, filtering, output cap, examples, and error codes. With a simple parameter set, strong annotations, and an output schema present, nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Context reports 0% schema description coverage, so the description must compensate. It explains asset as a client-side filter with examples and clarifies what `fraction` means for amounts. `response_format` is not mentioned in the description, but the schema already describes it, so this is a minor gap.

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?

States exactly what it does: shows the decimal precision (`fraction`) Convert accepts per asset. It also names the endpoint and explicitly differentiates itself from binance_get_convert_pairs, so an agent can select it without opening the schema.

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 (before binance_get_convert_quote, when a quote is rejected for precision) and When NOT to Use (pairs/min-max, pointing to binance_get_convert_pairs). It also includes examples and error-handling guidance, leaving no ambiguity about when to invoke it.

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