Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_otc_get_order

Retrieve the status and details of a specific OTC trade order by order ID, including coins, amounts, exchange rates, and creation time.

Instructions

Get detailed information about a specific OTC (Over-The-Counter) trade order.

Use this to check the status and details of a previously placed OTC order.

Response includes:

  • quoteId: Original quote ID used

  • orderId: Order identifier

  • orderStatus: SUCCESS, PROCESS, ACCEPT_SUCCESS, or FAIL

  • fromCoin/fromAmount: Sold coin and amount

  • toCoin/toAmount: Bought coin and amount

  • ratio/inverseRatio: Exchange rates

  • createTime: Order creation timestamp

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orderId": "<orderId>"
    },
    "name": "binance_us_otc_get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesOTC order ID to query (e.g., '10002349')

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

A3.6/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 behavioral burden. It discloses the return shape and the possible orderStatus values (SUCCESS, PROCESS, ACCEPT_SUCCESS, FAIL), which is substantive, but says nothing about authentication requirements, rate limits, or what happens for an unknown orderId.

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?

The purpose sentence is front-loaded, followed by a compact bulleted response breakdown; nothing is redundant. The field list is somewhat long, but each entry conveys distinct information an agent would otherwise lack given there is no output schema.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description compensates well by enumerating the returned fields and status values. Only ancillary details — auth scope and error behavior — are missing, which are minor for this complexity.

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 coverage is 100% and the single orderId parameter is already documented in the schema with an example value. The description only echoes 'quoteId'/'orderId' in the response list rather than adding new meaning to the input, so the baseline of 3 is appropriate.

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 detailed information about a specific OTC trade order' — which clearly separates it from the placement (binance_us_otc_place_order) and listing (binance_us_otc_all_orders) siblings. It stops short of naming an alternative explicitly, but the single-order scope is unambiguous.

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

Usage Guidelines4/5

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

It states the use case directly: 'Use this to check the status and details of a previously placed OTC order,' which tells the agent this is a post-trade lookup rather than a listing or creation call. No exclusions or prerequisites (e.g., quoting requirement) are given, so it falls short of a 5.

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