mcp-f1

Get Drivers

get_drivers

Fetch Formula 1 driver data from OpenF1 by session, meeting, team, or identity fields. Filter results using driver number, name acronym, or full name.

Instructions

Fetch F1 drivers from OpenF1, filtered by session, meeting or identity fields.

Input Schema

TableJSON Schema

Name	Required	Description
`full_name`	No	str — optional, 1-200 chars. Driver full name.
`last_name`	No	str — optional, 1-100 chars. Driver last name.
`team_name`	No	str — optional, 1-100 chars. Team name.
`first_name`	No	str — optional, 1-100 chars. Driver first name.
`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_code`	No	str — optional, 3 letters, normalized to uppercase. Deprecated by OpenF1 (removed after the 2026 season).
`name_acronym`	No	str — optional, exactly 3 letters (e.g., VER). Normalized to uppercase.
`driver_number`	No	int — optional, 1-99. Driver number for the season.

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.2/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 discloses almost nothing: it does not say what happens when no filters are supplied (all drivers?), whether filters combine as AND, whether results are paginated, or how 'latest' is interpreted. The only real behavioral hint is the upstream data source (OpenF1).

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?

A single tight sentence with the action and the filtering axes front-loaded; nothing is wasted, though there is also no supplementary structure such as notes on defaults.

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 nine optional parameters and an output schema present, the description need not explain return values, but for a zero-annotation tool it leaves open the default no-filter behavior and filter combination semantics. Adequate but with clear gaps.

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 is already documented with type, length, and normalization rules; the description only groups them into 'session, meeting or identity fields' and adds no syntax or precedence detail beyond the schema. Baseline 3 applies.

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 drivers from OpenF1') plus the supported filter dimensions, so the agent knows exactly what this returns. It does not compare itself to near neighbors like get_drivers_championship_view or get_session_results, so it falls short of a 5.

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?

The phrase 'filtered by session, meeting or identity fields' implies when this tool is appropriate (slicing the driver roster), but there is no explicit when-to-use guidance, no exclusions, and no named alternative for adjacent needs such as championship standings.

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