Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_ocbs_orders

Retrieve Binance.US One-Click-Buy-Sell fiat order history, including status, amounts, fees, and exchange rates; filter by date or order ID and paginate results.

Instructions

Query all OCBS (One-Click-Buy-Sell) fiat orders on Binance.US.

OCBS allows direct fiat-to-crypto conversions. This endpoint retrieves your OCBS order history for fiat transactions (e.g., USD to BTC).

Response includes:

  • total: Total number of OCBS orders

  • dataList: Array of orders with details

Each order contains:

  • quoteId, orderId, orderStatus (SUCCESS/FAIL)

  • fromCoin/fromAmount: Source currency and amount

  • toCoin/toAmount: Destination currency and amount

  • feeCoin/feeAmount: Fee details

  • ratio: Exchange rate

  • createTime: Order timestamp

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (starts from 1)
limitNoRecords per page (default: 10, max: 100)
endTimeNoEnd timestamp in milliseconds
orderIdNoFilter by specific order ID
startTimeNoStart timestamp in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
  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?

With no annotations supplied, the description carries the full load; it discloses that results are user-scoped order history and enumerates the returned fields, which is real behavioral value. However, it omits authentication requirements, rate limits, and pagination behavior, and the phrase 'Query all' sits awkwardly against a paginated endpoint with page/limit and a total count.

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?

Front-loaded with the purpose and the OCBS definition, then a compact bulleted response breakdown. The field list is long but earns its place given there is no output schema; a few entries (e.g., ratio, createTime) are near-obvious but harmless.

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 five-parameter, annotation-free, output-schema-free endpoint, the description does well on return shape by enumerating total/dataList and per-order fields. It still leaves material gaps an agent needs: whether the call is authenticated, what the default time range is, and how pagination interacts with 'all' orders.

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%, so page, limit, startTime, endTime, and orderId are already documented in the schema. The description says nothing about the time-window filters or the default range when startTime/endTime are omitted, so it adds no meaning beyond the structured data.

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 gives a specific verb and resource ('Query all OCBS ... fiat orders on Binance.US') and explains what OCBS means, which effectively distinguishes this from spot-order siblings like binance_us_all_orders or the OTC sibling. It stops short of naming any alternative explicitly, so the differentiation is implicit rather than stated.

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 by the context sentence 'OCBS allows direct fiat-to-crypto conversions' and 'retrieves your OCBS order history', which tells an agent this is the fiat-conversion history endpoint. There is no explicit when-to-use/when-not-to-use guidance and no mention of prerequisites (e.g., that it is a signed/user-scoped endpoint).

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