Formula One MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_event_scheduleA | Get Formula One race calendar for a specific season |
| get_event_infoB | Get detailed information about a specific Formula One Grand Prix |
| get_session_resultsC | Get results for a specific Formula One session |
| get_driver_infoC | Get information about a specific Formula One driver |
| analyze_driver_performanceC | Analyze a driver's performance in a Formula One session |
| compare_driversC | Compare performance between multiple Formula One drivers |
| get_telemetryC | Get telemetry data for a specific Formula One lap |
| get_championship_standingsC | Get Formula One championship standings |
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 8 tools
Mostly distinct: get_driver_info is reference data, get_session_results is outcomes, and get_telemetry focuses on lap data. However, compare_drivers and analyze_driver_performance both deal with performance analysis and could be confused in some agent workflows.
Six tools follow a clear get_<noun> pattern, while compare_drivers and analyze_driver_performance use verb_noun instead. This is a minor deviation but the verbs are meaningful and there is no mixed casing or chaotic style.
Eight tools is a well-scoped size for an F1 data server, covering schedules, events, sessions, standings, driver information, and analysis without excessive redundancy.
The set covers core read-only F1 workflows: calendar, event info, session results, standings, driver details, telemetry, and performance analysis. It lacks constructor/team-specific tools and some historical depth, but those are not critical gaps for a typical F1 data agent.