Skip to main content
Glama
Sign In
OpenF1 MCP Server

OpenF1 MCP Server

by ragulhari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Race control

get_race_control
Read-onlyIdempotent

Fetch Formula 1 race control messages including flags, safety car, DRS, penalties and track limits; filter by session, driver or time to track officiating and on-track incidents.

Instructions

Race control messages: flags, safety car, DRS, penalties, track limits, session status.

Input Schema

NameRequiredDescriptionDefault
flagNo"GREEN", "YELLOW", "DOUBLE YELLOW", "RED", "BLUE", "CHEQUERED", "BLACK AND WHITE", "CLEAR".
limitNoMaximum number of records to return (default 200, max 1000). A summary is added when the result is larger.
scopeNo"Track", "Driver", "Sector".
fieldsNoReturn only these attributes. Use this to make large results smaller.
date_toNoEnd of the time range (UTC, ISO 8601). Filters on "date" <= value.
filtersNoExtra comparison filters, e.g. [{"field":"lap_duration","op":"<","value":90}]. Allowed fields: category, date, driver_number, flag, lap_number, meeting_key, message, qualifying_phase, scope, sector, session_key. Array fields cannot be filtered.
categoryNo"Flag", "SafetyCar", "Drs", "CarEvent", "SessionStatus", "Other".
date_fromNoStart of the time range (UTC, ISO 8601), e.g. "2025-11-09T17:05:00Z". Filters on "date" >= value.
lap_numberNoLap number (starts at 1).
meeting_keyNoMeeting (Grand Prix weekend) identifier. Use "latest" for the current or most recent meeting.
session_keyNoSession identifier. Use "latest" for the current or most recent session.
driver_numberNoDriver number(s) for the season, e.g. 1, 44, 81. Give a list to get more than one driver.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds only content categories, not behavioral context such as ordering, pagination behavior, default result sizes, or how filtering affects results. It adds little beyond the safety profile already provided by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste. It states the resource and its content categories immediately, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 12 optional parameters and no output schema, the description is minimal but the schema is fully documented. It does not mention that the tool supports filtering by driver, session, meeting, date range, lap number, or custom filters, so an agent relying only on the description would miss major capabilities, though the schema compensates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 12 parameters thoroughly, including enums for flag, scope, and category. The description contributes no additional parameter meaning, which is acceptable at the baseline given complete schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as race control messages and enumerates the kinds of content returned (flags, safety car, DRS, penalties, track limits, session status). It lacks an explicit verb and does not differentiate from siblings, but the resource is unambiguous and unlike any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the content list: an agent can infer this tool is for race control messages. However, there is no explicit when-to-use guidance, no prerequisites, and no named alternatives or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools