Skip to main content
Glama
f1verse MCP Server

f1verse MCP Server

by jinsim

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

Formula 1 data with the domain rules already applied. Resolve vague references first: f1_season_status turns 'the last race' into a round number. For a whole race prefer f1_race_story over several narrow calls. Results are provisional until the stewards finish — within a few hours of a session, check f1_data_quality before calling anything final. A skipped check is unavailable evidence, not agreement. Read f1verse://guide for analysis workflows and coverage. Prompts are starting instructions, not fetched results. Live-feed race tools cover 2023 onward; careers and records reach back to 1950.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
f1_source_statusA

Last observed access state for each data source. No network probe. Distinguishes authentication, rate limits, availability and sources not yet checked in this process.

f1_race_eventsA

Evidence-linked race and pit-cycle events. Stable event IDs, input lineage and observed gap changes. No causal strategy claim or media download.

f1_turning_pointsA

Ranked retrospective race turning-point candidates. Ranks observed events by an explicit fixed event-kind heuristic. Uses future race information; not a live forecast or win-value model.

f1_pace_changesC

Persistent retrospective pace shifts within clean stints. Adjacent clean-lap windows, with trend removed, detect pace changes. Excluded laps are boundaries; the method does not identify a cause.

f1_retirement_riskA

Observed retirement survival across selected settled races. All-cause Kaplan-Meier over completed laps. Finishes are censored. Not a calibrated future reliability forecast; causes are unavailable.

f1_race_storyA

Everything that happened in one race, as structured JSON. The whole race in one call: final results with broadcast-convention gaps, lead changes, laps led per driver, the event timeline, tyre stints, median race pace (pit/SC/VSC laps excluded), and safety-car interruptions. Use this first for any 'what happened in race X' question — it is one request instead of six.

f1_race_briefA

A short factual race summary in plain English. A publishable prose summary of a race, built from templates only — every number in it comes from the data, so it is safe to quote verbatim. Use when the user wants a readable recap rather than fields to compute with.

f1_session_resultsA

Classification for any session of a weekend. Results for one session, classified the way that kind of session actually is: races give position and gap (lapped cars as '+1 LAP'), qualifying gives per-segment times with gaps to that segment's fastest and where each driver was eliminated, practice gives a best-lap table.

f1_weekend_sessionsA

Which sessions a given round has, in order. Lists the sessions of a race weekend with start and end times — the valid inputs for the 'session' argument of the other tools. Call this when unsure whether a round was a sprint weekend.

f1_season_statusA

Where the season stands right now and what is next. The latest completed race, sessions that have finished and settled, the next session and how many hours until it starts. Use this to answer 'when is the next race' or to resolve 'the last race' into a concrete round number before calling the other tools.

f1_standingsB

Championship standings after the latest completed round. Drivers' or constructors' championship table, with points and wins, as of the most recent round that has been scored.

f1_driver_careerA

A driver's career totals, 1950 to today. Starts, wins, podiums, poles and points for one driver across all of F1 history, plus the next round-number milestones they are approaching. Takes an Ergast-style driver id such as 'max_verstappen', 'hamilton' or 'leclerc'.

f1_data_qualityA

Is this session's data complete, current and safe to publish? Completeness per field, how old the fetched copy is, whether the classification is still provisional (stewards rewrite results hours after the flag), corrections observed so far, agreement between independent sources, and a single 'publishable' verdict. Call this before stating a result as final, especially within a few hours of a session ending.

f1_tyre_wearA

How fast each set of tyres degraded, stint by stint. Raw clean-stint lap-time trends and fuel-scenario corrected degradation, with exclusions, sample sizes and sensitivity. 2026+ corrected wear requires an explicit fuel_model; without it only raw trends are available. Earlier default coefficients are illustrative assumptions, not measured fuel. Circuit abrasion is a scenario index, not a measured surface property.

f1_deleted_lapsA

Lap times the stewards struck out, with reinstatements. Every lap-time deletion race control announced in a session, with the car, the time, the stated reason, and whether the deletion still stands — a reinstated lap is reported with the reversal visible rather than silently dropped. Use before treating a fastest lap or a qualifying position as settled.

f1_running_orderA

Who was where at the end of every lap. The order on track lap by lap, plus how much each lap churned and who made the biggest single gain. This is the data behind any position-change chart; use it for 'how did the race unfold' rather than fetching results and guessing.

f1_battlesA

Pairs that ran nose-to-tail, and for how long. Every stretch where two cars held consecutive positions within 1.5 seconds for at least three laps, with the closest the gap got. Finds the fights a results table hides — a scrap for eighth that ran twenty laps never shows up in the standings.

f1_archive_raceA

A race from 1996-2022, before the live-timing feeds. Results, lap-by-lap running order, lead changes and laps led for the seasons the modern feeds do not cover. Pit stops are included from 2011. The reply carries a 'coverage' block naming exactly what that era does and does not hold, so an absent field is never mistaken for a zero. Use f1_race_story for 2023 onward — it knows strictly more.

f1_closest_titlesA

Championships ranked by how close they finished. The smallest title margins in history, measured both in points and relative to what a win was worth that season — the only way seasons decades apart compare honestly, since two points in 1958 is most of a win and two points today is not.

f1_season_shapeB

How a championship unfolded, round by round. Each contender's running points total, who led after every round, and where the lead changed hands. Two seasons can end on the same margin and look nothing alike; this is what tells a procession from a fight.

f1_highlightsA

The stretches of a race worth watching. Windows where the timing feed's own passing signals cluster, ranked by density. An editing index rather than a verdict — it says where cars were changing state, not that a pass completed. 2023 onward.

f1_title_raceA

Championship win probability, and who is still mathematically alive. Two answers to 'who wins the title', kept deliberately apart. First the arithmetic: maximum points still available, and who is therefore out for certain — a fact, not a forecast. Then the projection: the rest of the season simulated thousands of times, resampling each driver from the positions they have actually finished in, with retirements at their measured rate. Every run first re-draws the driver's own level, so a short season widens the answer rather than hiding inside it. Returns the assumptions and sample sizes it stands on; the same seed returns the same numbers.

f1_circuit_profileA

A circuit's layout, pit-loss economics and historical record. Geometry, corner-by-corner lap position and local heading change, mini-sector and marshal-sector boundaries, pit loss under green/SC/VSC, a reference lap, and historical outcomes in one evidence-labelled profile. Coordinate length is explicitly not presented as surveyed metres; absent elevation, width and DRS geometry are named rather than guessed. Use this for a race-preview track explainer.

f1_circuit_surveyA

The circuit measured from the cars that drove it. What no public circuit map carries, measured from telemetry instead: the height profile with gradients and total climb; where overtakes actually happen, clustered into zones and merged across the timing line; how much of the lap is spent at full throttle and where the braking zones are, with entry and minimum speeds; the width of road the field used and the camber of it. DRS zones are included for seasons that had DRS and reported as a regulation change, not a weather excuse, for those that do not. Every figure names the laps and drivers behind it and declines rather than guesses when the samples cannot support it. Use for track explainers and previews that need real numbers, not an outline.

f1_circuit_directoryA

Every Formula 1 venue recorded in the historical results. A source-labelled directory of circuit ids, names, cities, countries and coordinates from 1950 to today. This is the discovery call for a historic venue; pass its id to f1_circuit_history for results, and use f1_circuit_profile with a year and round when the question needs that event's specific layout.

f1_circuit_historyA

A Formula 1 venue's winners, pole conversion and records. Historical results at one circuit: every event count, recent winners and their starting positions, pole-to-win conversion, and the most successful drivers. Use f1_circuit_directory first to discover the stable circuit id; this is results history, so it does not assign a modern map to an older layout.

Prompts

Interactive templates invoked by user choice

NameDescription
race-briefExplain a race with lifecycle, source checks and labelled uncertainty.
strategy-reviewReview pit exchanges and pace with assumptions and causal limits.

Resources

Contextual data attached and managed by the client

NameDescription
Analysis guide
Current tool catalogue

TDQS

B3.4/5.0

Scored across 26 tools

Disambiguation3/5

Descriptions carefully carve out boundaries, but several clusters overlap heavily: f1_race_story aggregates results, running order, timeline and stints that f1_session_results, f1_running_order and f1_race_events also expose. Likewise f1_race_events vs f1_turning_points, and f1_circuit_profile vs f1_circuit_survey vs f1_circuit_history, require reading long descriptions to choose correctly. The guidance is good, but an agent can still reasonably hesitate among multiple 'what happened' or 'circuit' tools.

Naming Consistency4/5

Every name uses the same f1_ prefix and snake_case, and follows a predictable f1_<domain>_<object> style. The names are mostly noun phrases rather than verb_noun actions, but the convention is consistent throughout with only minor semantic variation (e.g. f1_closest_titles, f1_season_shape).

Tool Count3/5

At 26 tools the surface is heavy, well above the comfortable 3-15 range. The breadth of F1 analysis, history and circuit data justifies many of them, but some analytics variants could be consolidated or exposed as options on fewer tools. It is borderline rather than clearly excessive.

Completeness4/5

Coverage is unusually broad: live/settled sessions, standings, race narratives, tyre and pace analysis, history, circuits and championship projections are all represented. Minor gaps remain around general driver/team directories, a full season calendar, and some race-control/penalty information beyond deleted laps, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues