Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_open_order_lists

Read-onlyIdempotent

Get every open order list still working across all symbols, so you can see what is already armed before placing a new bracket.

Instructions

List the order lists that are still working, across every symbol.

Calls GET /api/v3/openOrderList (SIGNED, IP weight 6). The endpoint takes no filters — it is account-wide by construction, which is exactly what makes it the right first read before placing another bracket.

When to Use:

  • Before placing a new bracket, to see what is already armed on the same position.

  • After a 5xx/timeout on a placement, when you have no id to query.

When NOT to Use:

  • For one known list — binance_get_order_list (weight 4).

  • For lists that already finished — binance_get_all_order_lists.

  • For plain open orders — binance_get_open_orders (spot_orders.py); a list's legs also appear there individually.

Returns: A markdown table (time, symbol, orderListId, contingencyType, listStatusType, listOrderStatus, listClientOrderId, leg count) capped at 50 rows, or the raw array with response_format="json".

Examples: params = {} params = {"response_format": "json"}

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

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?

Beyond the readOnlyHint/idempotentHint annotations, the description discloses the API endpoint, SIGNED requirement, IP weight 6, lack of filters, output format details, the 50-row cap, and the -2015 error meaning. It also notes that an empty list is a valid response, which prevents false interpretation.

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, front-loaded purpose, and no filler. Every sentence adds decision-relevant information, such as when to call, when not to call, return shape, and error handling.

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 description is complete for a read-only one-parameter tool: it covers use cases, exclusions, output format, examples, and error semantics. The return behavior is fully specified, and the annotations cover the safety profile, so nothing needed for correct invocation 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?

The description explains the only parameter, response_format, by specifying the markdown vs json behaviors and providing two concrete examples. Even though context reports 0% schema description coverage, the description fully compensates by documenting the parameter and its allowed values.

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 order lists that are still working, across every symbol' is a specific verb+resource statement that clearly distinguishes this from siblings like binance_get_all_order_lists and binance_get_open_orders. It also clarifies the account-wide scope, which is a key differentiator.

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 explicitly provides 'When to Use' and 'When NOT to Use' sections. It names exact sibling tools (binance_get_order_list, binance_get_all_order_lists, binance_get_open_orders) and the conditions that route an agent to each alternative.

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