Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_open_orders

Read-onlyIdempotent

List orders currently resting on Binance's order book. Specify a symbol for a lightweight query, or omit to check every pair. Returns markdown or JSON.

Instructions

List the orders currently resting on the book.

Calls GET /api/v3/openOrders (SIGNED). Weight 6 with symbol, 80 without — the no-symbol form scans every pair and costs more than a percent of the 6000/min IP budget in one call. Pass a symbol whenever you know it.

When to Use:

  • To see what is working right now, before placing or cancelling anything.

  • After a 5xx/timeout on a placement, as a symbol-wide check when you have no id.

When NOT to Use:

  • For one known order — binance_get_order costs weight 4 and is precise.

  • For orders that are no longer open — binance_get_all_orders covers history.

Returns: A markdown table (time, symbol, orderId, side, type, status, price, origQty, executedQty, cumQuote) capped at 50 rows, or the raw array with response_format="json".

Examples: params = {"symbol": "BTCUSDT"} params = {}

Error Handling: -2015 means the key lacks permission or this IP is not allowlisted. An empty list is a valid answer: nothing is resting.

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 mark this as read-only and idempotent, but the description adds substantial behavioral context beyond that: it is a SIGNED call, the weight difference between 6 and 80 is called out, the no-symbol form scans every pair, error -2015 is explained, and an empty list is confirmed as a valid result. This goes well beyond what the annotations alone provide.

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 organized with clear headers and front-loads the most important operational constraint (weight/cost) before usage guidance. Every section — returns, examples, error handling — serves a distinct purpose, and nothing feels redundant or filler.

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?

The definition covers what the tool does, when to use it, when not to use it, the cost implications, exact return format, example params, and error semantics. Given the annotations and output schema, there are no missing operational details an agent would need to call this tool correctly.

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 schema gives descriptions for `symbol` and `response_format`, the description reinforces the critical trade-off (weight 6 with symbol vs 80 without), gives exact example parameter objects, and explains how `response_format="json"` changes the output. This compensates for the low schema description coverage signal and gives an agent enough detail to invoke the tool correctly.

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 opening sentence, 'List the orders currently resting on the book,' uses a specific verb and resource that exactly matches the tool name and endpoint. The later 'When NOT to Use' section explicitly distinguishes it from `binance_get_order` and `binance_get_all_orders`, so an agent can select it correctly without ambiguity.

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 provides dedicated 'When to Use' and 'When NOT to Use' sections with concrete scenarios: checking working orders before placing/cancelling, recovering after a 5xx/timeout, and avoiding it for single-order lookups or historical orders. It names the alternative tools (`binance_get_order`, `binance_get_all_orders`) and the conditions that route to them.

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