pmxt-mcp

Official

Overview Schema Source Related Servers Discussions Admin

fetchOHLCV

Read-only

Retrieve historical candlestick price data for prediction market outcomes. Specify exchange, outcome ID, time range, and resolution to get aggregated OHLCV data.

Instructions

Fetch historical OHLCV (candlestick) price data for a specific market outcome.

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>",
      "outcomeId": "<outcomeId>"
    },
    "name": "fetchOHLCV"
  }
}

Input Schema

Name	Required	Description
`exchange`	Yes	The prediction market exchange to target.
`outcomeId`	Yes
`resolution`	No	Required for candle aggregation
`start`	No	Start of the time range
`end`	No	End of the time range
`limit`	No	Maximum number of results to return
`verbose`	No	Return full uncompacted response. Default false returns a compact, agent-friendly summary.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.46.14May 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the tool is read-only. The description adds minimal context beyond that (historical data). It does not disclose any additional behavioral traits like data granularity, pagination, or rate limits.

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 sentence that is concise and front-loaded. It could be slightly more structured, but it earns its place without waste.

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?

Given the tool has 7 parameters and no output schema, the description is too minimal. It does not explain the return format, what OHLCV represents, or how the resolution parameter affects output. More context is needed for an agent to use this tool effectively.

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 86%, so the baseline is 3. The description does not add meaning beyond what the schema provides; each parameter is already described in the schema.

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 clearly states the tool fetches historical OHLCV (candlestick) data for a specific market outcome, using a specific verb and resource. It does not explicitly distinguish from sibling tools like fetchTrades or fetchOrderBook, but the OHLCV concept is distinct enough.

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 on when to use this tool versus alternatives. With many sibling fetch tools, the description does not help the agent decide whether to use fetchOHLCV over fetchMarket or fetchTrades.

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