Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_all_oco_orders

Fetch all OCO order history on Binance.US with optional time-range and pagination filters; returns up to 1,000 orders for trade review and auditing.

Instructions

Get all OCO orders (history) on Binance.US. Returns up to 1000 orders.

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_all_oco_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (default 500, max 1000)
fromIdNoOrder list ID to start from. Cannot be used with startTime/endTime.
endTimeNoEnd time in milliseconds. Cannot be used with fromId.
startTimeNoStart time in milliseconds. Cannot be used with fromId.
recvWindowNoReceive window in milliseconds (max 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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses a result cap of 1000 orders, which is useful, but says nothing about authentication requirements, rate limits, default page size (500, only in the schema), sort order, or whether pagination via fromId is forward or backward in time.

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, front-loaded with the resource and scope. Nothing is wasted, though the 1000-order cap duplicates the schema's limit max and could have been spent on more useful behavioral detail.

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

Completeness2/5

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

Five optional parameters, no annotations, and no output schema, yet the description never explains what an OCO order record contains or how the list is ordered across pages. For a history-listing endpoint where pagination semantics matter, this is thin.

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?

Schema description coverage is 100%, covering limit, fromId, startTime/endTime and their mutual exclusivity, and recvWindow. The description adds no parameter meaning beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('Get all OCO orders (history) on Binance.US'), which separates it from single-order lookups like binance_us_get_oco. The 'history' qualifier implies it covers closed/filled OCO orders rather than only live ones, but that contrast with binance_us_open_oco is never made explicit.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over binance_us_open_oco, binance_us_get_oco, or binance_us_all_orders. The agent must infer that 'history' means past orders and must guess at prerequisites; nothing states it requires authenticated account access.

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