Quote.Trade MCP Adapter

Quote.Trade current/open orders

quote_trade_get_orders

Read-only

Anytime order check. POST /api/getOrders with per-request X-MBX-APIKEY. Read-only: no live trading action. Requires read entitlement on API keys that carry one.

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": "quote_trade_get_orders"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional maximum number of orders to return.
`symbol`	No	Optional instrument symbol filter, such as BTC. Omit for all symbols.
`endTime`	No	Optional inclusive end of a time range, epoch milliseconds.
`startTime`	No	Optional inclusive start of a time range, epoch milliseconds.

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.

AddedSep 17, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful context: per-request X-MBX-APIKEY, no live trading action, and the need for read entitlement. This goes beyond the annotations by naming the auth mechanism and access precondition.

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?

Three short, purposeful sentences with the purpose front-loaded and no filler. 'Anytime order check' is slightly vague, but the endpoint, auth, and read-only status are conveyed efficiently.

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?

Given the output schema, full parameter coverage, and annotations covering safety, the description supplies the remaining essentials: endpoint, API key requirement, and read entitlement. It omits minor details like default behavior when no params are supplied, but nothing critical is missing for a read-only query tool.

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 all four optional parameters already documented in the input schema. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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?

Description opens with 'Anytime order check' and names the POST /api/getOrders endpoint, making the action and resource clear. It does not explicitly distinguish itself from siblings like get_order_history or get_order_status; that distinction is left to the title's 'current/open orders' phrasing.

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

Usage Guidelines2/5

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

No when-to-use or alternative guidance is provided beyond the vague 'Anytime order check.' It states the read-only nature and entitlement requirement, but never explains when to choose this over get_order_status or get_order_history.

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?