Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_get_oco

Retrieve details of a specific OCO order on Binance.US by providing either the order list ID or original client order ID.

Instructions

Query a specific OCO order on Binance.US. Either orderListId or origClientOrderId must be provided.

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

Input Schema

NameRequiredDescriptionDefault
recvWindowNoReceive window in milliseconds (max 60000)
orderListIdNoThe order list ID to query
origClientOrderIdNoThe original client order ID to query

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
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. 'Query' implies a read-only operation, but it says nothing about permissions/auth needs, what happens if both IDs are supplied, error behavior for unknown IDs, or rate limits. It adds only a single input constraint.

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?

Two short sentences, purpose first and constraint second, with no filler or repetition. Every sentence carries information the agent needs.

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 read-only lookup with fully documented params and no output schema, this is adequate but thin: it omits auth requirements and the shape of the result. The mutual-exclusivity rule is the main completeness win.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning the schema lacks: the schema marks zero required parameters, so the explicit 'either orderListId or origClientOrderId must be provided' rule is the only statement of the mutual requirement. recvWindow is left entirely to the schema.

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 states a specific verb and resource ('Query a specific OCO order') and scopes it to Binance.US. It implicitly distinguishes itself from the sibling binance_us_all_oco_orders (plural/all) but never names any alternative explicitly.

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?

It gives one useful usage rule: either orderListId or origClientOrderId must be supplied. It does not say when to prefer this over binance_us_get_order, binance_us_open_oco, or binance_us_all_oco_orders, nor any prerequisites such as authentication.

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