Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai

binance_get_order_rate_limits

Read-onlyIdempotent

Check current order-rate-limit usage (per-second/day counts) before placing orders or to debug -1015 rejections. Returns interval, limit, and used count for each ORDERS window.

Instructions

Get the account's current order-rate-limit usage (per-second/day order counts).

Calls GET /api/v3/rateLimit/order (SIGNED, USER_DATA). IP weight 40 per call — noticeably heavier than the other tools in this module; do not poll this tightly.

When to Use:

  • Before a burst of order placements, to see how much of the ORDERS rate limit (per interval, e.g. 10s/1d) has already been used.

  • To debug a -1015 "Too many orders" rejection.

When NOT to Use:

  • For the exchange-wide REQUEST_WEIGHT/RAW_REQUESTS limits — those come back in every response's rate-limit headers, not from this endpoint.

Returns: A markdown list (or JSON) of {rateLimitType, interval, intervalNum, limit, count} entries — one per configured ORDERS rate-limit window.

Examples: params = {}

Error Handling: -2015 means the key lacks Reading permission or the 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

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds valuable context beyond those: it discloses that the endpoint is SIGNED, has IP weight 40 with a caution not to poll tightly, and explains the -2015 error status. No contradiction exists.

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 longer than average but every section earns its place: purpose, usage, non-usage, return format, example, and error handling are clearly separated under headers. It remains scannable and front-loaded with the core purpose.

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 read-only, idempotent tool with a single optional parameter and rich annotations, the description covers usage scenarios, exclusions, IP weight, error handling, and return content. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema exposes only the 'params' object with 'response_format', and the description mentions 'params = {}' and 'markdown list (or JSON)'. However, it does not explicitly tie the response_format parameter to the output format, and the schema description already covers that parameter meaning, so the description adds limited new semantic value.

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: 'Get the account's current order-rate-limit usage (per-second/day order counts).' It explicitly identifies the endpoint and clearly differentiates itself from exchange-wide request-weight limits, so an agent can distinguish this from sibling tools without reading 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?

The 'When to Use' and 'When NOT to Use' sections give explicit contexts: use before bursts of order placements or when debugging -1015 errors, and do not use for REQUEST_WEIGHT/RAW_REQUESTS limits. This leaves no ambiguity about when to select this tool versus alternatives.

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