Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_rate_limits

Retrieve current trade order count rate limits for all time intervals to see how many orders you can place within each interval.

Instructions

Get current trade order count rate limits for all time intervals. Shows how many orders you can place within each interval.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "binance_us_rate_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
recvWindowNoThe value cannot be greater than 60000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Get' and 'Shows' establish a read-only, non-mutating operation and the second sentence hints at the returned data (order counts per interval), but it says nothing about authentication requirements, request weight/rate-limit cost, or whether intervals are fixed — gaps an agent would care about for a rate-limit endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the resource stated up front and the interpretation ('how many orders you can place') immediately after. The second sentence is partly a restatement of the first but does add usable meaning about the returned numbers, so waste is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-optional-parameter read endpoint with no output schema, the description covers what the tool returns at a high level but not the shape of the response (interval buckets and limit values). It is adequate but leaves the agent guessing at the returned structure.

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?

There is a single optional parameter (recvWindow) with 100% schema description coverage, so the schema already explains it. The description adds nothing about timing semantics or defaults, which is the expected baseline-3 outcome when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource — 'Get current trade order count rate limits for all time intervals' — and scopes it to every interval, so an agent knows exactly what data comes back. It does not name or contrast with any sibling tool, but the resource is distinct enough (rate limits vs. orders/account endpoints) to identify.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: an agent would call this to learn how many orders it may place in each interval before submitting orders. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative endpoint, leaving the agent to infer the pre-trade-check workflow.

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