mcp_f1_strategy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_race_stateC | Raw session snapshot at a given lap: position, gap to leader/car ahead, tire compound and tire age for every driver still classified. |
| get_tire_degradation_curveB | Calibrated tire degradation model (base pace + degradation rate) for a compound at a circuit, fit on real FastF1 lap data. |
| get_pit_loss_timeA | Time lost by pitting at this circuit (in-lap + pit lane + out-lap, minus a green-flag lap), from real FastF1 data when available. |
| get_pit_windowB | Optimal pit window for |
| simulate_undercut_overcutB | Compares pitting |
| compare_strategy_optionsA | Projects total remaining-race time for N hypothetical strategies (each: a label, a list of pit laps, and a list of compounds — one more compound than pit laps) for the same driver. |
| get_historical_strategiesA | Real stint breakdown (compound, start/end lap) and finish position from past race sessions at this circuit. |
| predict_finish_positionA | Projects |
| generate_strategy_reportA | Formats a Markdown strategy report from an LLM/host-curated list of decisions. Purely deterministic formatting — no summarization here. |
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 9 tools
Most tools have clear, separate roles: data retrieval (race state, degradation, pit loss), tactical comparison (pit window, undercut/overcut), and broader strategy projection (compare strategies, predict finish). There is minor overlap among the strategy-decision tools—compare_strategy_options could technically reproduce an undercut/overcut comparison—but descriptions distinguish intent well enough.
All tools follow a consistent snake_case verb_noun pattern, dominated by get_ for data/model lookups and simulate/compare/predict/generate for analysis actions. No style or verb inconsistency exists.
Nine tools is well-scoped for an F1 strategy assistant: a handful of data/model inputs, a few decision/analysis operators, and one report formatter. Each tool earns its place without redundancy.
The set covers the core strategy workflow—reading session state, modeling tires/pit loss, evaluating windows and under/overcuts, comparing multi-stop strategies, predicting finish, and producing a report. Obvious peripheral gaps like weather or fuel effects are absent, but they are not essential to the stated purpose.