QuantXData MCP Server

get_trades

Retrieve historical trade executions for any trading pair on a supported exchange, using optional start/end timestamps and a result limit to tailor the query.

Instructions

Get historical trade executions from an exchange

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": {
      "exchange": "<exchange>",
      "instrument": "<instrument>"
    },
    "name": "get_trades"
  }
}

Input Schema

Name	Required	Description
`to`	No	End timestamp (ISO 8601 format, optional)
`from`	No	Start timestamp (ISO 8601 format, optional)
`limit`	No	Maximum number of results (default: 100)
`exchange`	Yes	Exchange name (e.g., binance, coinbase, kraken)
`instrument`	Yes	Trading pair (e.g., BTC/USDT, ETH/USD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it gets historical trades, but does not mention pagination behavior, response format, or any read-only guarantees. This leaves significant ambiguity for an agent selecting this 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?

The description is a single, focused sentence that is concise and front-loaded. It earns its place by stating the essential purpose, though it is perhaps too terse to compensate for lack of other details.

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

Completeness2/5

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

For a tool with 5 parameters and no output schema or annotations, the description is thin. It lacks information about return values, time-range behavior, or how it differs from similar sibling tools, making it incomplete for an agent to fully understand context.

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?

The schema description coverage is 100%, so all parameters are already well-described in the schema. The description adds no additional semantic information about parameters, so the baseline score of 3 applies.

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?

The description specifies the action 'Get' and the resource 'historical trade executions' from an exchange, which is clear and non-tautological. However, it does not differentiate from sibling tools like get_multi_trades or get_ohlcv, so the uniqueness is limited.

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 guidance is provided on when to use this tool versus alternatives such as get_multi_trades or stream_realtime. The description simply states what it does without any context about use cases or exclusions.

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

Deploy Server