mcp-f1

Get Sessions

get_sessions

Fetch Formula 1 sessions (practice, qualifying, sprint, race) from OpenF1 by year, location, meeting, or session type to find event schedules and IDs.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	int — optional, >= 2023 (OpenF1 data starts in 2023).
`location`	No	str — optional, 1-100 chars, e.g., 'Spa-Francorchamps'.
`circuit_key`	No	int — optional, positive int. Circuit identifier.
`meeting_key`	No	int \| str — optional, positive int or 'latest'. Meeting (Grand Prix weekend) identifier.
`session_key`	No	int \| str — optional, positive int or 'latest'. Session identifier; 'latest' targets the current/most recent session.
`country_name`	No	str — optional, 1-100 chars, e.g., 'Belgium'.
`session_name`	No	str — optional, e.g., 'Practice 1', 'Qualifying', 'Race'.
`session_type`	No	str — optional, e.g., 'Practice', 'Qualifying', 'Race'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it offers almost nothing beyond 'Fetch'. It does not state that this is a read-only lookup, how multiple filters combine (AND vs OR), how 'latest' is resolved, or any pagination/ordering behavior. No contradiction, but a significant disclosure gap for an 8-param query tool.

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 tight sentence, front-loaded with the verb and resource plus a useful parenthetical scope. No filler or redundancy.

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?

An output schema exists, so return values need not be explained. However, with 8 optional filters, no annotations, and no statement about how filters interact or when this tool is the right entry point versus get_meetings/get_session_results, the definition is only minimally complete for an agent to select and call it confidently.

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%, with each parameter documented in the schema (ranges, examples such as 'Spa-Francorchamps', 'latest' semantics), so the schema does the heavy lifting. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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 verb ('Fetch') and resource ('F1 sessions') and clarifies the domain concept by enumerating session kinds (practice, qualifying, sprint, race). It does not, however, distinguish itself from nearby siblings like get_meetings or get_session_results, which an agent must infer from the name alone.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives such as get_meetings (weekend-level) or get_session_results (results within a session). Usage is only implied by the resource name; there are no exclusions, prerequisites, or filter-combination hints.

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