therundown-data
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THERUNDOWN_API_KEY | Yes | Your TheRundown API key, sent as X-TheRundown-Key header. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sportsA | List current canonical sport IDs and names. Do not use a catalog row as evidence of current events, prices, or plan access. |
| list_affiliatesA | List currently published affiliate IDs and names, excluding retired affiliates. Do not use a catalog row as proof of plan access or an open offer for a sport or market. |
| list_marketsA | Discover market definitions, or available markets for one sport and date. Do not use definitions as price quotes or combine live with date-based discovery. Catalog sport/live filters use catalog metadata. |
| list_eventsA | Find event IDs and summaries for one sport and date. Do not use this tool for futures or as a price quote; use the returned exact event ID with get_main_lines. Defaults to open main lines for prematch markets 1/2/3 and affiliates 19/23. Each local page refetches a metered snapshot. |
| get_main_linesA | Fetch open per-affiliate main lines for one event_id. Do not call until list_events returned that exact ID, and do not treat retrieved_at as price freshness. Preserves participant identity, line value and price updated_at. Request live markets 41/42/43 explicitly; each local page is metered. |
| list_futuresA | Read one sport's scoped futures competition page. Do not use this for dated event discovery or treat a partial page as a complete listing. Futures require an eligible Ultra plan or higher and use opaque cursor pagination. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| brief | Rules for scoped requests, price evidence, billing, credentials, and the first conversation. |
TDQS
Scored across 6 tools
The tools have distinct core functions: listing sports, affiliates, markets, events, futures, and fetching main lines. However, list_markets and list_futures both involve markets, and list_events and get_main_lines are closely related, which could cause some confusion for an agent about when to use each.
All tool names follow a consistent snake_case verb_noun pattern (list_sports, list_affiliates, list_markets, list_events, get_main_lines, list_futures). The only slight deviation is get_main_lines, but it still fits the verb_noun structure.
Six tools is a well-scoped number for a data retrieval server covering sports, affiliates, markets, events, and futures. Each tool serves a distinct purpose without excessive redundancy.
The server covers discovery of sports, affiliates, markets, events, and futures, plus retrieval of main lines. However, it lacks tools for accessing other types of odds or markets beyond main lines, and no write operations are present, though that may be outside the domain scope.