Skip to main content
Glama

TheRundown Data MCP

Get futures for a sport

v2GetFuturesForSport
Read-onlyIdempotent

Get futures for a sport Returns futures/outright competition events (e.g. tournament winner) for a sport, with future-class markets in the standard V2 market → participants → lines → prices shape and per-market settlement state. Competition events are excluded from the dated game endpoints and served only here. Early access — requires an Ultra plan or higher.

A competition is an interval, not an instant: event_date is when it starts and settle_by is when it must have graded. Futures events carry no teams array and no score — the human-readable identity is schedule.event_name.

Date filtering uses interval overlap. An event is returned when its [event_date, settle_by] span intersects the requested window — settle_by >= from and event_date <= to. So the default from=now means "in flight right now" and matches a season future that started months ago.

Paging is keyset-based (no skip parameter). When more results exist the response carries meta.next_cursor; pass it back verbatim as cursor. Ordering is soonest-to-resolve first: settle_by, then event_date, then event_id. meta.count is the number of events on the page, meta.has_more says whether another page exists, and meta.total is the number of events matching your filters across all pages, so a single call tells you the size of the listing.

Default visibility: settled markets are removed per market, an event is hidden once every requested future-class market on it has settled, and terminal (final/canceled/abandoned) events are excluded. include_settled=true lifts all of those and the default from=now, so settled history is reachable.

Delta bootstrap: On known zero-delay access, meta.delta_last_id can seed GET /api/v2/markets/delta only when this snapshot explicitly reports X-Data-Delay-Seconds: 0; it is a positive whole-integer cursor. With a positive, absent, or invalid delay header, keep using scoped snapshots and do not substitute 0. Futures market IDs are not in the delta feed's default set — pass them explicitly (e.g. market_ids=1141) when polling. See the Futures guide for the full integration recipe. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
queryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
planNo
emptyNo
errorNo
usageNo
statusNo
messageNo
event_idNo
source_urlNo
retry_afterNo
limit_reasonNo
retrieved_atNo
required_planNo
remaining_pointsNo
missing_entitlementNo
monthly_remaining_pointsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the read-only/idempotent safety profile, but the description adds substantial non-structured context: the Ultra-plan access gate, per-market settlement removal and terminal-event hiding, exactly what include_settled=true lifts (including the default from=now), the delta-feed caveat that futures market IDs are not in the default delta set, and the no-background-polling/no-retry constraint. These are real behavioral traits beyond what annotations disclose.

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?

Purpose is front-loaded and the body is organized into bolded sub-topics (date filtering, paging, visibility, delta bootstrap), which is appropriate for a complex tool. It is dense and long, and the trailing generic boilerplate ('Read-only Product data...', 'No wagers, account changes or guarantee of returns') adds less value than the rest.

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

Completeness5/5

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

For a tool with an output schema and full annotations, the description covers the remaining gaps an agent needs: access tier, interval semantics, keyset paging, default visibility, settled-history behavior, and delta-feed interaction. Nothing required to call it correctly is missing.

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?

Although the reported schema coverage is 0%, the input schema itself carries rich per-parameter prose (interval semantics for from/to, offset timezone minutes, cursor opacity, market_ids intersection with future-class markets, include_settled effects). The description largely restates this interval-overlap and pagination behavior rather than adding new meaning, so it sits at the baseline of 3.

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 states a specific verb and resource ('Get futures for a sport') and immediately narrows scope to 'futures/outright competition events (e.g. tournament winner)', explicitly noting that competition events are excluded from the dated game endpoints and served only here. This lets an agent distinguish it from list_futures, v2GetFuturesEventByID, and the dated event endpoints without opening any schema.

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

Usage Guidelines4/5

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

It clearly establishes when this tool is the right one ('competition events are excluded from the dated game endpoints and served only here') and gives the Ultra-plan prerequisite. It does not, however, name the sibling to use for a single futures event (v2GetFuturesEventByID) or contrast with list_futures, so routing to alternatives is left partly to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.