F1 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_race_scheduleB | Get the race schedule for a specific F1 season |
| get_session_resultsC | Get results for a specific F1 session (practice, qualifying, or race) |
| get_driver_standingsC | Get driver championship standings for a season |
| get_constructor_standingsC | Get constructor championship standings for a season |
| get_lap_timesC | Get lap times for a specific session |
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 has a clearly distinct purpose targeting different F1 data aspects: constructor standings, driver standings, lap times, race schedule, and session results. No overlap exists, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive nouns (e.g., get_constructor_standings, get_driver_standings). This uniformity enhances predictability and readability.
Five tools are reasonable for an F1 data server, covering key standings and session data. It's slightly lean but well-scoped; minor gaps like historical data or driver details might exist but don't hinder core functionality.
The tool set covers essential F1 queries: standings, schedules, lap times, and session results. Minor gaps include lack of update/delete operations (typical for read-only data) and potential missing features like pit stop times or weather data, but core workflows are supported.