Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_otc_place_order

Place an OTC trade order using a quoteId from a prior Binance.US OTC quote; quotes expire quickly, so submit the order immediately.

Instructions

Place an OTC (Over-The-Counter) trade order using a previously acquired quote.

⚠️ IMPORTANT: You must first call binance_us_otc_quote to get a quoteId before placing an order. The quote expires quickly, so place the order immediately after receiving the quote.

Order Status values:

  • PROCESS: Order is being processed

  • ACCEPT_SUCCESS: Order accepted, awaiting completion

  • SUCCESS: Order completed successfully

  • FAIL: Order failed

Response includes:

  • orderId: Unique order identifier

  • createTime: Order creation timestamp

  • orderStatus: Current status of the order

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": {
      "quoteId": "<quoteId>"
    },
    "name": "binance_us_otc_place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYesQuote ID received from binance_us_otc_quote (e.g., '4e5446f2cc6f44ab86ab02abf19a2fd2')

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

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and delivers a lot: a mandatory workflow dependency, a quote-expiry constraint, the meaning of each order status, and the shape of the response (orderId, createTime, orderStatus). It stops short of stating whether a placed OTC order can be cancelled or what permissions/funds are required, which is a meaningful gap for a mutating trade tool.

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 action, then a warning, then reference material — good structure with headers and bullets. The status enumeration is slightly long but earns its place because no output schema exists to document the return values.

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

Completeness5/5

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

For a one-parameter mutation with no annotations and no output schema, everything an agent needs is present: the prerequisite, the timing constraint, and the returned fields with status semantics. Nothing essential is left to structured data that does not exist.

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% and the single parameter already has a description, so the baseline is 3. The description earns an extra point by explaining where the quoteId comes from and that it is short-lived, which affects how the agent must source and use the value.

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 ('Place an OTC trade order') and the key precondition ('using a previously acquired quote'), which cleanly separates it from binance_us_otc_quote and the order-retrieval siblings like binance_us_otc_get_order.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite tool (binance_us_otc_quote), states the condition that makes it necessary (need a quoteId), and adds timing guidance ('quote expires quickly, so place the order immediately'). An agent needs no inference to know when and how to sequence this call.

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