Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_SPORT_LOG_LEVELNoLog level on stderr (DEBUG, INFO, WARNING, ERROR).INFO

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_driversB

Fetch F1 drivers from OpenF1, filtered by session, meeting or identity fields.

get_sessionsB

Fetch F1 sessions (practice, qualifying, sprint, race) from OpenF1.

get_meetingsC

Fetch F1 meetings (Grand Prix or testing weekends) from OpenF1.

get_session_resultsA

Fetch the final classification of an F1 session from OpenF1.

Results become available a few minutes after the official results are published on the Formula 1 website. If the API returns HTTP 404, the results are not yet published for that session — retry with an earlier session_key (use get_sessions to find completed sessions).

get_starting_gridA

Fetch the starting grid for an F1 race from OpenF1.

Grid data becomes available a few minutes after the official results are published on the Formula 1 website. If the API returns HTTP 404, the grid is not yet published for that session — retry with an earlier session_key (use get_sessions to find completed sessions).

get_positionsC

Fetch driver position changes throughout an F1 session from OpenF1.

get_lapsC

Fetch detailed lap-by-lap data for an F1 session from OpenF1.

get_pit_stopsC

Fetch pit lane passes for an F1 session from OpenF1.

get_stintsC

Fetch tyre stints (periods of continuous driving) from OpenF1.

get_intervalsA

Fetch real-time gaps between drivers and to the race leader from OpenF1.

Available during races only, with updates approximately every 4 seconds. Use date_from/date_to to bound the response (e.g., the closing laps).

get_race_controlC

Fetch race control events (flags, safety car, incidents) from OpenF1.

get_weatherC

Fetch weather conditions over the track from OpenF1 (sampled every minute).

get_overtakesA

Fetch overtakes during F1 races from OpenF1.

Covers on-track passes and position changes from pit stops or post-race penalties. Only available during races and may be incomplete.

get_team_radioA

Fetch team radio exchanges between drivers and teams from OpenF1.

Only a limited selection of communications is included, not the complete record. Coverage has decreased significantly starting in 2026, with most events providing no radio data at all (a limitation on F1's side).

get_car_dataA

Fetch car telemetry (speed, rpm, gear, throttle, brake, DRS) from OpenF1.

Sampled at ~3.7 Hz — always narrow down with the range filters below (e.g., a single lap via date_from/date_to, or high-speed samples via speed_min) to keep responses usable.

get_locationA

Fetch approximate car positions on the circuit from OpenF1.

Sampled at ~3.7 Hz — always narrow down with date_from/date_to (e.g., a single lap) to keep responses usable. Useful for gauging progress along the track, but lacks lateral placement (left/right side). The origin point (0, 0, 0) is arbitrary.

get_drivers_championshipA

Fetch drivers championship standings from OpenF1 (beta endpoint).

Only available for race sessions. This endpoint is in beta: its behavior or fields may change without notice.

get_teams_championshipA

Fetch teams championship standings from OpenF1 (beta endpoint).

Only available for race sessions. This endpoint is in beta: its behavior or fields may change without notice.

get_drivers_championship_viewA

Fetch drivers championship standings and render them as a visual board.

MCP App spike (task 05): in hosts supporting the MCP Apps extension, the result renders as an interactive HTML board with driver photos, team colors and points. In other hosts, the same data is returned as JSON text.

get_race_replay_viewA

Replay a race as an animated position chart (bar-chart-race style).

MCP App (task 06): in hosts supporting the MCP Apps extension, renders cars stacked by official position with a checkered treadmill paced by the leader (a new lap opens when the leader crosses), tyre compound badges (red S / yellow M / white H), per-sector times with broadcast colors recomputed at the displayed instant (one purple per sector, green = personal best, yellow = slower), the lap time as MM:SS:mmm, PIT badges, a centered Safety Car / VSC / race-suspended banner, and a header with circuit, local start time and track conditions. Retired cars show a permanent OUT or DNS tag and drop gap, sectors and lap time. In other hosts the same payload is returned as JSON text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
standings_viewHTML view for the drivers championship standings MCP App.
race_replay_viewHTML view for the animated race replay MCP App.

TDQS

A3.5/5.0

Scored across 20 tools

Disambiguation4/5

Most tools target clearly distinct F1 data endpoints (weather, laps, pit stops, car data, etc.), but get_drivers_championship and get_drivers_championship_view fetch the same standings with different rendering, which could cause selection confusion. get_race_replay_view also partially overlaps with position/location tools, though its replay purpose is described distinctly.

Naming Consistency5/5

All tools follow a consistent get_<resource> snake_case pattern (e.g., get_weather, get_drivers, get_laps). The two view tools add a predictable _view suffix, so the naming remains coherent and readable.

Tool Count4/5

20 tools is on the heavy side, but the F1 data domain is broad and each tool maps to a distinct OpenF1 endpoint or presentation layer. The count is reasonable rather than bloated, though it could be tightened by merging the championship view with its data tool.

Completeness5/5

The set covers the full OpenF1 read-only surface: sessions, meetings, drivers, results, grids, positions, laps, pit stops, stints, intervals, race control, overtakes, radio, telemetry, location, and both championships. The added view tools provide optional rendering without leaving obvious gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues