Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_convert_open_limit_orders

Read-onlyIdempotent

List currently resting convert limit orders with expiry times to avoid duplicate placements and confirm whether an order was placed after a timeout.

Instructions

List the convert limit orders currently resting on the account.

Calls GET /sapi/v1/convert/limit/queryOpenOrders (SIGNED, UID weight 3000 of a 180,000/min budget) — cross-asset, no filters, so poll it sparingly.

When to Use:

  • To see what convert limit orders are live, with their expiry instants.

  • Before placing another one, to avoid stacking duplicates.

  • After a timeout on a placement, to learn whether the order actually rested.

When NOT to Use:

  • For completed conversions — binance_get_convert_history.

  • For spot open orders — binance_get_open_orders.

Returns: One row per resting order: creation time, from → to amounts, ratio, status, orderId and the expiry instant. Markdown display caps at 50 rows.

Examples: params = {}

Error Handling: -2015 means the key lacks permission or the IP is not allowlisted; 429 on /sapi means the UID budget is gone — this endpoint alone is 3000 per call.

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?

While annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, the description adds substantial behavioral context: the endpoint's weight (3000) and budget (180,000/min), a caution to poll sparingly, specific error codes (2015 for permissions, 429 for rate limit), and the exact return fields per row. This goes far beyond the annotations, giving the agent critical operational knowledge.

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 sections, bullet points, and an example. Every sentence serves a purpose: purpose, usage guidance, return format, example, and error handling. The most critical info (what it does and when to use it) is front-loaded, and there is no redundant fluff. The length is justified by the richness of the content.

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 tool is a read-only query with rate-limit implications, and the description covers all necessary aspects: purpose, usage scenarios, return format (fields per row), error handling, rate limit budget, and the example invocation. Even though an output schema exists, the description adds clarity about the return fields and markdown cap. Nothing an agent needs to decide whether to call this tool and interpret its results 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?

The schema has 0% description coverage for parameters, and the single parameter (params) is an object with response_format. The description compensates by providing an example 'params = {}' and noting 'Markdown display caps at 50 rows', which clarifies the markdown format behavior. It does not fully explain the json output variant, but the schema itself already has a description for response_format ('markdown or json output'), so the addition is marginal but still useful.

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 specific verb and resource: 'List the convert limit orders currently resting on the account.' It names the exact API endpoint and clearly distinguishes from siblings like binance_get_convert_history (completed conversions) and binance_get_open_orders (spot orders). The purpose is unambiguous and immediately actionable.

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 includes dedicated 'When to Use' and 'When NOT to Use' sections with concrete scenarios (e.g., before placing another order to avoid duplicates, after a timeout to check if the order rested). It explicitly names the alternative tools for completed conversions and spot orders, leaving no ambiguity about when this tool is appropriate.

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