amazing-binance-mcp

Overview Schema Source Related Servers Discussions Admin

binance_test_order

Read-onlyIdempotent

Validate a Binance order against exchange filters before placing it, catching precision and rule errors without sending it to the order book. Confirms the order would pass, preventing failed real orders.

Instructions

Validate an order against Binance's filters WITHOUT sending it to the order book.

Calls POST /api/v3/order/test (SIGNED, IP weight 1 — 20 with compute_commission_rates). Binance runs the same validation as a real placement (signature, recvWindow, symbol status, LOT_SIZE / PRICE_FILTER / NOTIONAL, balance rules) and returns {} on success: nothing is matched, nothing rests on the book, no funds move.

This tool is always allowed. It is on the client's POST_READ_ALLOWLIST, so it works with the trading kill-switch off (BINANCE_ALLOW_TRADING unset) — which makes it the right first step before every binance_place_order call.

When to Use:

Always, immediately before placing a real order, to catch a filter or precision error for free.
With compute_commission_rates=true to learn the fee rates that would apply.

When NOT to Use:

To actually trade — that is binance_place_order.
To check a symbol's filters in the abstract — binance_get_exchange_info (market_data.py) lists tick size, step size and min notional directly.

Returns: A confirmation that the order passed validation (and the commission-rate breakdown when requested). A rejection comes back as an Error: line quoting Binance's reason.

Examples: params = {"symbol": "BTCUSDT", "side": "BUY", "type": "LIMIT", "time_in_force": "GTC", "quantity": "0.001", "price": "20000.00"} params = {"symbol": "BTCUSDT", "side": "SELL", "type": "MARKET", "quantity": "0.001", "compute_commission_rates": True}

Error Handling: -1013/-2010 point at a symbol filter (step size, tick size, min notional); -1111 is a precision error — check binance_get_exchange_info. -2015 means the key lacks Spot Trading permission or this IP is not allowlisted. The per-type mandatory parameter sets are checked locally, so those failures never reach Binance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds substantial behavioral context: it runs the same validation as a real placement, returns {} on success, never matches or rests on the book, and is always allowed even with the trading kill-switch off. It also discloses error semantics and IP weight. This goes well beyond the 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?

The description is well-structured with clear sections: purpose, when to use, when not to use, returns, examples, and error handling. Every sentence earns its place, and the most important scoping information is front-loaded. Despite its length, it is efficiently organized for an agent to parse.

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?

Given the tool's complexity, the description is complete: it covers the endpoint, safety profile, usage context, return behavior, error codes, and provides two concrete examples. The output schema exists, so return values need not be fully re-explained. Nothing an agent needs to call this correctly 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?

Schema description coverage is 0% for the top-level params object, but the nested TestOrderInput schema is extremely rich, documenting every field with Binance names, formats, and per-type mandatory sets. The description adds value by explaining the compute_commission_rates weight increase and the local validation of mandatory parameter sets. Since the schema already carries the heavy lifting, a 4 is appropriate.

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?

The description opens with a precise verb and resource: 'Validate an order against Binance's filters WITHOUT sending it to the order book.' It names the exact endpoint, distinguishes itself from real order placement, and clearly differentiates from siblings like binance_place_order and binance_get_exchange_info. The purpose is unmistakable.

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?

The description has explicit 'When to Use' and 'When NOT to Use' sections. It states to always use before binance_place_order, and explicitly excludes actual trading (binance_place_order) and abstract filter checks (binance_get_exchange_info). This is exemplary routing guidance.

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

Deploy Server