TheRundown Data MCP

Get market price history for an event

v2GetMarketHistoryByEvent

Read-onlyIdempotent

Get market price history for an event Returns recorded price changes for the requested markets and sportsbooks, subject to your plan's historical-data access. Data can be available before, during, or after an event as prices are recorded. Each response is bounded by the requested limit. Read-only Product data or price calculation. Use returned canonical IDs. Access, delay and metered usage follow your connected account; never infer coverage from an empty result. One bounded request, no background polling or automatic retry. Affiliate 27 is excluded. No wagers, account changes or guarantee of returns.

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": {
      "path": "<path>"
    },
    "name": "v2GetMarketHistoryByEvent"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`query`	No

Output Schema

Name	Required	Description	Default
`data`	No
`plan`	No
`empty`	No
`error`	No
`usage`	No
`status`	No
`message`	No
`event_id`	No
`source_url`	No
`retry_after`	No
`limit_reason`	No
`retrieved_at`	No
`required_plan`	No
`remaining_points`	No
`missing_entitlement`	No
`monthly_remaining_points`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: metered usage/access delay tied to the connected account, a single bounded request with no polling or retry, affiliate 27 exclusion, and the caveat not to infer coverage from an empty result.

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

Conciseness3/5

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

The purpose is front-loaded, but it is delivered as a run-on ('...for an event Returns recorded price changes...') followed by a long trail of compliance-style statements that read partly as boilerplate. Several sentences (no wagers, no account changes) do little to help an agent invoke the tool.

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?

With an output schema present, return-format detail is not required, and the annotations cover the safety profile. Combined with the access/metering, bounding, and empty-result caveats, this is close to complete; the main remaining gap is routing against sibling history tools.

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?

Top-level schema coverage is reported as 0%, so the description should carry more weight, though the nested property descriptions are in fact rich (market_ids default/cap, affiliate_ids list, main_line semantics). The description only implicitly signals filtering by markets/sportsbooks, the affiliate 27 exclusion, and canonical IDs, adding little syntax or default detail beyond 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 opening sentence names a specific verb (Get) and resource (market price history for an event), which is unambiguous on its own. However, it does not differentiate from close siblings such as v2GetMarketLineHistoryByEvent or v2GetMarketLinePriceHistory, which an agent must disambiguate before choosing this tool.

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?

It gives contextual guidance about historical-data access being plan-dependent and prices being recorded before/during/after an event, and warns that empty results do not imply missing coverage. But it names no alternative tool and gives no explicit when-to-use-this-vs-sibling rule, which matters in a family containing several near-identical history endpoints.

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

All TheRundown Data MCP 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.