Quote.Trade MCP Adapter

Quote.Trade place live order

quote_trade_place_order

Destructive

Trade step 4. POST /api/order with a suitable price after instruments/ticker/depth. Requires tradingEnabled, allowedSymbols (* or explicit list; empty denies), and API credentials. No MCP USD notional cap applies. Sending X-MBX-APISECRET to this MCP host grants it full signing authority. humanApproved/approvalText are agent friction only.

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": {
      "account": "<account>",
      "symbol": "<symbol>",
      "side": "<side>",
      "price": "<price>",
      "quantity": "<quantity>",
      "humanApproved": "<humanApproved>",
      "approvalText": "<approvalText>"
    },
    "name": "quote_trade_place_order"
  }
}

Input Schema

Name	Required	Description
`side`	Yes	BUY or SELL.
`type`	No	LIMIT only in this adapter.
`price`	Yes	Limit price chosen after quote_trade_depth.
`symbol`	Yes	Instrument symbol from quote_trade_instruments, such as BTC.
`account`	Yes	Quote.Trade account/user id. Optional for preview (defaults to account init-param, QUOTE_TRADE_ACCOUNT, or 0). Required for live place_order.
`quantity`	Yes	Order quantity.
`timestamp`	No	Optional client timestamp in milliseconds.
`approvalText`	Yes	Agent-supplied confirmation friction (not a security control). Must exactly equal: APPROVE QUOTE.TRADE LIVE ORDER
`humanApproved`	Yes	Agent-supplied confirmation friction (not a security control). Must be true; enableTrading remains authoritative.
`disableLeverage`	No	1 disables leverage; 0 enables leverage/shorting only if server allowLeverage is true.
`paymentCurrency`	No	Payment currency such as USDT.

Output Schema

Name	Required	Description
`raw`	Yes	Raw JSON response body.
`body`	Yes	Parsed JSON response body when valid JSON; otherwise the raw text.
`method`	Yes	HTTP method used against Quote.Trade.
`status`	Yes	HTTP status code.
`endpoint`	Yes	Quote.Trade API endpoint path.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 6, 2026

changedInput schema / properties / humanApproved / description

Previous value: -"Agent-supplied confirmation friction (not a security control). Must be true; server-side enableTrading/allowedSymbols/maxNotionalUsd remain authoritative."New value: +"Agent-supplied confirmation friction (not a security control). Must be true; enableTrading remains authoritative."

changedInput schema / properties / price / description

Previous value: -"Limit price."New value: +"Limit price chosen after quote_trade_depth."

changedInput schema / properties / symbol / description

Previous value: -"Symbol such as BTC."New value: +"Instrument symbol from quote_trade_instruments, such as BTC."

Changed1 schema field changedAug 5, 2026

changedInput schema / properties / account / description

Previous value: -"Quote.Trade account/user id. Can default from account init-param or QUOTE_TRADE_ACCOUNT."New value: +"Quote.Trade account/user id. Optional for preview (defaults to account init-param, QUOTE_TRADE_ACCOUNT, or 0). Required for live place_order."

First observedAug 5, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial behavioral context beyond the annotations: no MCP USD notional cap applies here, sending X-MBX-APISECRET grants the host full signing authority, and humanApproved/approvalText are explicitly labeled as friction rather than security controls. That is materially more than destructiveHint/openWorldHint convey.

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-loads the workflow step and endpoint, then packs prerequisites, auth, and caveats into a few dense sentences with no filler. The telegraphic style is efficient, though a couple of clauses (e.g. allowedSymbols parenthetical) could be tightened.

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 high-stakes live-order tool with an output schema already covering returns, the description supplies the missing risk context: gating flags, credential/signing implications, and the fact the USD notional cap does not apply. Nothing an agent needs to call this safely is absent.

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 11 parameters, and the baseline is 3. The description only adds that price should be chosen after quote_trade_depth and that no notional cap applies, which is marginal beyond the structured fields.

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+resource ('place live order', POST /api/order) and situates it as 'Trade step 4' after instruments/ticker/depth, which distinguishes it from the read-only siblings. It stops short of explicitly contrasting with quote_trade_order_preview, so a perfect 5 isn't warranted.

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?

Gives clear sequencing ('step 4 ... after instruments/ticker/depth') and states prerequisites (tradingEnabled, allowedSymbols, API credentials), which tells the agent the context in which this tool is callable. It never names the dry-run alternative (quote_trade_order_preview) or says when not to use it, which keeps it below 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Quote.Trade MCP Adapter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?