AI Race Engineer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key. Only needed for the agent (strategy) server. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_session_infoA | Load an F1 session and return its metadata and driver list. Args: year: Season, 2018 or later (FastF1 coverage starts in 2018). circuit: Event or location name, e.g. "Austria", "Monza". session_type: "R" race, "Q" qualifying, "S" sprint, "FP1"/"FP2"/"FP3". |
| get_driver_stintsC | Per-stint compound, lap range and length for one driver. Args: driver: Three-letter code, e.g. "VER", "NOR", "LEC". |
| get_degradationA | Fitted tyre degradation per stint for one driver. Lap times are cleaned (safety car, VSC, in/out and inaccurate laps removed) and
fuel-corrected before fitting. Each stint reports an R² and a |
| compare_driversB | Stint-by-stint degradation comparison across several drivers. Args: drivers: Three-letter codes, e.g. ["VER", "NOR", "LEC"]. |
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 4 tools
The tools are largely distinct: session loading, stint data, degradation modeling, and multi-driver comparison. The only potential overlap is between get_degradation and compare_drivers, but the single-vs-multi-driver distinction is clear from descriptions.
Three tools follow the 'get_' verb-noun pattern, while compare_drivers uses a different verb without 'get'. This is a minor deviation, but the names remain predictable and readable overall.
With 4 tools, the server is well-scoped for its tyre-focused purpose. It covers the essential workflow without bloat, though it is on the smaller side, leaving room for additional specialized tools.
The server covers the full tyre degradation analysis lifecycle: session loading, stint retrieval, degradation fitting, and cross-driver comparison. Minor gaps like raw lap times or session context tools exist, but they are not critical for the stated purpose.