Skip to main content
Glama
PrimeGoose

f1-telemetry-mcp

by PrimeGoose

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOSTNoHost for the Streamable HTTP transport (default 127.0.0.1).
PORTNoPort for the Streamable HTTP transport (default 3333).
MCP_TRANSPORTNoTransport mode. Set to "http" to use the Streamable HTTP transport; defaults to stdio.
F1_SESSION_FILENoPath to a session JSON file to load instead of the bundled sample session.

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
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_session_summaryB

Overview of the loaded session: driver, circuit, laps, fastest lap, top speed, final tyre wear.

get_lap_timesC

Lap and sector times for every lap.

compare_lapsA

Compare two laps: total and per-sector delta, plus time delta by distance (positive = lapB slower).

get_fastest_sectorC

Fastest time for a given sector and the theoretical best lap.

find_braking_pointsB

Detect braking zones on a lap (start/end distance, entry and minimum speed).

get_tyre_wearB

Tyre wear (%) per corner per lap and average wear rate.

get_car_telemetryB

Speed/throttle/brake/gear/RPM samples for a lap within a distance range (downsampled to maxPoints).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
session-summarySummary of the loaded session
Lap 1Lap metadata (times, sectors, tyre wear) without raw samples
Lap 2Lap metadata (times, sectors, tyre wear) without raw samples
Lap 3Lap metadata (times, sectors, tyre wear) without raw samples
Lap 4Lap metadata (times, sectors, tyre wear) without raw samples
Lap 5Lap metadata (times, sectors, tyre wear) without raw samples
Lap 6Lap metadata (times, sectors, tyre wear) without raw samples
Lap 7Lap metadata (times, sectors, tyre wear) without raw samples
Lap 8Lap metadata (times, sectors, tyre wear) without raw samples

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct analytical purpose, even when operating on similar underlying data. Lap timing tools are separated into listing, comparison, and fastest-sector extraction, while telemetry tools are separated into raw sample retrieval and braking-zone detection.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (get_*, compare_*, find_*). The verbs are predictable and accurately describe the action.

Tool Count5/5

Seven tools is a well-scoped set for F1 telemetry analysis. Each tool covers a distinct analysis need without obvious redundancy or bloat.

Completeness4/5

The surface covers session overview, lap timing, comparison, tyre wear, braking analysis, and raw telemetry. Minor gaps remain, such as weather, track position, stint/compound data, or pit-stop analysis, but core telemetry workflows are well covered.

Maintenance

ActivityMaintained
ResponsivenessNo issues