Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_all_orders

Read-onlyIdempotent

Retrieve all order statuses for a trading pair within a 24-hour window or page forward using an order ID cursor to reconstruct historical activity.

Instructions

List a symbol's orders — open, filled, cancelled and expired alike.

Calls GET /api/v3/allOrders (SIGNED, IP weight 20). Two ways to narrow it: order_id as a cursor (returns orders with orderId >= it) or a start_time/ end_time window. The window may not exceed 24 hours — that cap is checked here, before the call, so you get a clear message instead of Binance's -1127. Walk a longer span in 24 h slices, or page by order_id.

When to Use:

  • Reconstructing what happened on a symbol in a given day.

  • Paging order history forward with an order_id cursor.

When NOT to Use:

  • For what is open right now — binance_get_open_orders (weight 6 with a symbol).

  • For the actual fills, fees and trade ids — binance_get_my_trades (trade_history.py); an order row only carries aggregates.

Pagination: limit is 1-1000 (Binance default 500) and at most 50 rows are rendered; use response_format="json" or narrow the window for the rest. order_id pages forward: pass the last orderId you saw, plus one.

Windows: start_time/end_time accept epoch ms or ISO-8601 and must span 24 h or less together. Omit both to get the most recent limit orders. Orders with no fill are archived after 90 days and stop being returned.

Examples: params = {"symbol": "BTCUSDT"} params = {"symbol": "BTCUSDT", "start_time": "2026-09-22T00:00:00Z", "end_time": "2026-09-22T23:59:59Z", "limit": 1000} params = {"symbol": "BTCUSDT", "order_id": 123456789}

Error Handling: A window wider than 24 h is rejected locally. -1127 from Binance means the same thing reached it anyway; -1121 is an unknown symbol. -2015 means the key lacks 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=true and idempotentHint=true, and the description adds substantial behavioral context beyond them: the call is SIGNED with IP weight 20, the 24-hour window cap is validated locally, only 50 rows are rendered, and orders without fills are archived after 90 days. This gives an agent accurate expectations about rate limits, pagination, and data availability.

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 long but highly structured with clear sections, bullet lists, and concrete examples. Every section adds operational value: pagination, window rules, use cases, exclusions, and error handling. The critical 24-hour constraint is prominently highlighted, and the formatting makes the length scannable.

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 network-backed read tool with pagination, time windows, and auth requirements, the description covers endpoint details, local validation, limits, paging strategies, error codes, and example parameter sets. With an output schema present, no return-format explanation is needed, and nothing required to call the tool correctly is missing.

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?

Even though the nested schema has some parameter descriptions, the signal reports 0% schema description coverage, so the plain-language description carries the burden. It explains order_id cursor semantics ('orderId >= this'), start_time/end_time accepted formats (epoch ms or ISO-8601), the 24-hour span constraint, default behavior when both are omitted, and the effect of response_format, all beyond the schema fields.

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 states a specific verb and resource ('List a symbol's orders') and immediately clarifies scope: open, filled, cancelled and expired alike. It distinguishes itself from sibling tools like binance_get_open_orders and binance_get_my_trades, so an agent can select it correctly without opening schemas.

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?

Dedicated 'When to Use' and 'When NOT to Use' sections explicitly route to alternatives: binance_get_open_orders for currently open orders and binance_get_my_trades for fills/fees/trade IDs. It also explains when to use order_id paging versus time windows, leaving no ambiguity.

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