Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

openf1_race_control

Retrieve Formula 1 race-control messages by session or date range, filtered by category, flag, scope, lap, driver, or sector to track incidents, safety cars, DRS, and session status.

Instructions

OpenF1 Formula 1 race control messages. Returns race-control messages: session status, incidents, flags, safety car and DRS events, with category, flag, scope, sector, lap number, qualifying phase and the message text. Use session_key for one session, or a date window to sweep a range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openf1_race_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagNoFlag type, one of BLACK AND WHITE, BLUE, CHEQUERED, CLEAR, DOUBLE YELLOW, GREEN, RED, YELLOW Enums(BLACK AND WHITE,BLUE,CHEQUERED,CLEAR,DOUBLE YELLOW,GREEN,RED,YELLOW) example(BLACK AND WHITE)
scopeNoEvent scope; one of Track, Driver, Sector Enums(Track,Driver,Sector)
filterNoRepeatable upstream filter written as <attribute><operator><value>, with operators >=, <=, =, > and <. Repeated filters on the same attribute are OR'ed, a lower and upper bound form an inclusive range, and different attributes are AND'ed. Filterable attributes on this route: meeting_key, session_key, date, driver_number, lap_number, category, flag, scope, sector, qualifying_phase, message.
sectorNoTrack sector the message refers to, starting at 1
date_toNoInclusive upper bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-08)
categoryNoRace-control category, one of CarEvent, Drs, Flag, Other, SafetyCar, SessionStatus Enums(CarEvent,Drs,Flag,Other,SafetyCar,SessionStatus) example(Flag)
date_fromNoInclusive lower bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-07)
lap_numberNoLap number within the session, starting at 1 example(8)
meeting_keyNoPositive meeting key from openf1-meetings, or `latest` for the current meeting example(1299)
session_keyNoPositive session key from openf1-sessions, or `latest` for the current session example(11408)
driver_numberNoPositive permanent driver number (see openf1-drivers) example(1)
qualifying_phaseNoQualifying phase, 1 to 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Returns' implies a read-only listing and it usefully enumerates the fields returned (category, flag, scope, sector, lap number, qualifying phase, message text), which partly substitutes for a missing output schema, but it says nothing about pagination, result ordering, rate limits, or what an unfiltered call yields.

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

Conciseness4/5

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

Three sentences, front-loaded with the resource and its return contents before the scoping advice. The opening fragment 'OpenF1 Formula 1 race control messages' slightly duplicates the second sentence's opening, but otherwise there is no wasted wording.

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?

For a 12-parameter, fully-optional tool with no annotations and no output schema, the description covers what comes back and how to scope by session or date. It leaves gaps on default behavior with zero filters, result volume/limits, and ordering, which matter for a broad sweep tool.

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 every parameter including the complex repeatable filter syntax is already fully documented in the schema. The description adds only the session_key-vs-date-window decision, which is a modest semantic addition over structured fields and warrants the baseline.

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?

States a specific resource (OpenF1 race-control messages) and enumerates the concrete content types returned: session status, incidents, flags, safety car and DRS events. An agent can tell this apart from data-plane siblings like openf1_car_data or openf1_team_radio, though it never explicitly names or contrasts a sibling.

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

Usage Guidelines4/5

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

The final sentence gives actionable scoping guidance: use session_key for a single session, or a date window to sweep a range. That is clear context for how to call it, but there are no exclusions (e.g., when to prefer openf1_laps or openf1_sessions instead) and no mention of behavior with no parameters at all.

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