QuantXData MCP Server

get_multi_trades

Retrieve consolidated trade data across multiple exchanges with filters for time range, currencies, and result limit. Combine trading activity from various markets into one query.

Instructions

Get consolidated trade data across multiple exchanges

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": {
      "exchanges": "<exchanges>"
    },
    "name": "get_multi_trades"
  }
}

Input Schema

Name	Required	Description
`to`	No	End timestamp
`from`	No	Start timestamp
`limit`	No	Max results
`exchanges`	Yes	Array of exchange names
`base_currencies`	No	Array of base currencies (e.g., ["BTC", "ETH"])
`quote_currencies`	No	Array of quote currencies (e.g., ["USDT", "USD"])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden. It discloses the consolidating behavior and multi-exchange scope, but lacks detail on return format, ordering, approximation behavior, or potential errors. As a read-only 'Get' tool, the safety is implicit, but deeper behavioral context is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that gets straight to the point with no filler. Every word contributes to understanding the tool's core function.

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

Completeness3/5

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

While the description is clear, it lacks an explicit statement about return value structure (no output schema), how 'consolidated' is achieved, or how filters interact across exchanges. Combined with the schema, it is minimally adequate but leaves operational uncertainty.

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 input schema already provides full descriptions for all six parameters (100% coverage), so the description does not need to repeat them. It adds no additional parameter semantics 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?

The description uses a specific verb 'Get' with a resource 'consolidated trade data' and explicitly scopes it 'across multiple exchanges', clearly distinguishing it from the sibling tool get_trades which likely handles single-exchange trades.

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 implies usage for retrieving trade data from multiple exchanges at once, but does not explicitly state when to use it over get_trades or provide any exclusions. The differentiation is only implicit via the phrase 'across multiple exchanges'.

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

Deploy Server