Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_otc_coin_pairs

Retrieve supported Binance.US OTC trading pairs with minimum and maximum limits to plan large block trades outside the regular order book.

Instructions

Get a list of supported OTC (Over-The-Counter) trading pairs on Binance.US.

OTC trading allows large block trades to be executed outside the regular order book, minimizing market impact. This endpoint returns available coin pairs with their minimum and maximum trading limits.

Response includes:

  • fromCoin/toCoin: The trading pair

  • fromCoinMinAmount/fromCoinMaxAmount: Min/max amounts for the sell coin

  • toCoinMinAmount/toCoinMaxAmount: Min/max amounts for the buy coin

Example: Convert large amounts of BTC to USDT without affecting market price.

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

Input Schema

NameRequiredDescriptionDefault
toCoinNoFilter by destination coin (e.g., USDT, KSHIB)
fromCoinNoFilter by source coin (e.g., BTC, SHIB)

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.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does useful work by enumerating the response fields (fromCoin/toCoin, min/max amounts) even though no output schema exists, but it omits auth requirements, rate limits, and whether the result is complete or paginated.

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 core purpose is front-loaded in the first sentence, and the following sentences each add something (what OTC is, response shape, example). The response field list is somewhat verbose but justified since there is no output schema; nothing is clearly redundant.

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 simple two-optional-filter lookup with no output schema, the description supplies enough: purpose, the domain concept, the returned fields, and a concrete example. The remaining gap is operational context (auth, limits), which is modest for a read-only listing endpoint.

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%, with both optional filters documented in the schema itself, so baseline 3 applies. The description reinforces the semantics by naming fromCoin/toCoin in the response field list, but adds no filtering syntax, matching behavior, or default-result guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Get a list of supported OTC (Over-The-Counter) trading pairs on Binance.US.' This is unambiguous and clearly distinct from the sibling order-placement/quote tools (binance_us_otc_quote, binance_us_otc_place_order), which act on trades rather than enumerating pairs.

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 explains what OTC trading is and gives a scenario ('Convert large amounts of BTC to USDT without affecting market price'), which implies when the tool is relevant. However, it never states a when-to-use rule relative to siblings, nor any prerequisite (e.g., this is a discovery/lookup step before quote or place_order). Guidance is implied rather than explicit.

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