racing-alpha-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RACING_ALPHA_API_KEY | No | Optional API key to increase rate limits. Get one at racingalpha.co.uk/developers and pass it as the RACING_ALPHA_API_KEY environment variable. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_today_racesA | Today's GB & IRE horse races with Racing Alpha's published model picks (advised prices are database-frozen at publication). Returns race ids usable with get_race_signals. |
| get_race_signalsA | Racing Alpha's derived signals for one race: per-runner AI score (0-100), de-overrounded fair price, value vs fair, plus race-level draw-bias verdict and the frozen model pick if the race made the public card. |
| get_tips_ledgerA | Racing Alpha's public tips ledger — every pick database-frozen at publication with result, level-stakes P/L, and closing-line-value summary. Includes losses; that is the point. |
| get_draw_biasA | 3-year draw-bias aggregates for GB & IRE flat courses: impact value (IV), actual/expected (A-E) and percentage-of-rivals-beaten (PRB) by stall third, per course, surface and distance band. |
| get_combo_statsB | Trainer×jockey combination strike rates over settled GB & IRE races in Racing Alpha's archive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct question: race lists, per-race signals, tips ledger, draw bias stats, and trainer-jockey combos. There is no functional overlap, making selection unambiguous.
All tools follow the same get_<object> pattern (e.g., get_today_races, get_race_signals). The naming is predictable and consistent.
Five tools is a well-scoped size for a horse racing tips-and-stats server. Each tool fills a clear role without redundancy or bloat.
The core workflow is covered: browse today's races, drill into signals, check historical tips, and consult statistical context. Minor gaps exist like historical racecards or non-today races, but they don't undermine the primary purpose.