Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_otc_quote

Request a time-limited OTC quote for converting one coin to another on Binance.US by specifying sell coin, buy coin, and amount; use the returned validTimestamp before the quote expires.

Instructions

Request a quote for an OTC (Over-The-Counter) trade on Binance.US.

This endpoint requests a price quote for converting one coin to another via OTC. The quote is valid for a limited time (check validTimestamp in response).

⚠️ IMPORTANT: The quote must be used quickly as it expires based on validTimestamp.

Parameters:

  • fromCoin: The coin you want to sell (e.g., BTC, SHIB)

  • toCoin: The coin you want to buy (e.g., USDT, KSHIB)

  • requestCoin: Which coin's amount you're specifying (must be fromCoin or toCoin)

  • requestAmount: The amount of the requestCoin

Response includes:

  • symbol: Trading pair symbol

  • ratio: Conversion ratio (e.g., 50550.26 for BTC/USDT)

  • inverseRatio: Inverse conversion ratio

  • validTimestamp: Unix timestamp when quote expires

  • toAmount/fromAmount: Calculated amounts for the trade

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": {
      "fromCoin": "<fromCoin>",
      "toCoin": "<toCoin>",
      "requestCoin": "<requestCoin>",
      "requestAmount": "<requestAmount>"
    },
    "name": "binance_us_otc_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toCoinYesCoin to buy (e.g., USDT, KSHIB)
fromCoinYesCoin to sell (e.g., BTC, SHIB)
requestCoinYesWhich coin's amount you're specifying (fromCoin or toCoin)
requestAmountYesAmount of the request coin

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?

With no annotations supplied, the description carries the full burden. It does disclose the most important behavioral trait — the quote expires at validTimestamp and must be consumed quickly — plus the returned fields. It omits whether the quote is binding, whether any funds are reserved, auth requirements, or rate limits, so meaningful gaps remain for a trading-adjacent endpoint.

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

Conciseness3/5

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

The expiry warning is well front-loaded and easy to spot, but the Parameters block duplicates a fully-described schema line for line, and the opening two sentences overlap in meaning. Trimming the parameter list would leave a tighter, equally informative definition.

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?

There is no output schema, so the 'Response includes' section earns its place by naming symbol, ratio, inverseRatio, validTimestamp, and computed toAmount/fromAmount. Combined with the expiry warning, an agent has enough to call the tool and interpret the result; only the downstream execution step and auth expectations are left implicit.

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 the schema already documents all four parameters, and the description's Parameters section largely restates them. It adds only example tickers (BTC, SHIB → USDT, KSHIB) and reinforces the fromCoin/toCoin relationship for requestCoin; the 'check validTimestamp' hint is the one genuinely additive note.

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: 'Request a quote for an OTC trade on Binance.US', with a follow-up sentence clarifying it returns a price quote for converting one coin to another. It clearly reads as a non-executing quote step, distinguishing it in practice from binance_us_otc_place_order, but it never names that sibling 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?

The description implies the workflow (get a quote, then act on it quickly before validTimestamp expires) and flags the time constraint prominently. However, it never states when to prefer this over binance_us_otc_coin_pairs or binance_us_otc_place_order, nor any prerequisites such as account eligibility or 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