mcp-f1

Get Overtakes

get_overtakes

Fetch Formula 1 race overtakes and position changes from pit stops or penalties using a session key. Filter by overtaking or overtaken driver number and post-overtake position.

Instructions

Fetch overtakes during F1 races from OpenF1.

Covers on-track passes and position changes from pit stops or post-race penalties. Only available during races and may be incomplete.

Input Schema

TableJSON Schema

Name	Required	Description
`position`	No	int — optional, >= 1. Position of the overtaking driver after the overtake.
`session_key`	No	int \| str — required in practice, positive int or 'latest'. Race session identifier; use get_sessions to discover it.
`overtaken_driver_number`	No	int — optional, 1-99. The passed driver.
`overtaking_driver_number`	No	int — optional, 1-99. The attacking driver.

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

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so reasonably: it discloses the availability window, that results "may be incomplete," and what event types are covered. It omits auth/rate-limit details, but for a read-only data fetch the disclosed caveats are the material ones.

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?

Three short sentences, front-loaded with the resource and immediately followed by scope and constraints. No filler or repetition of the title.

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

Completeness4/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 no explanation, and the description supplies the key caveats (availability window, possible incompleteness). It could be stronger by noting relationships to get_sessions or get_positions, but it is essentially complete for calling the 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 the schema already documents all four parameters, including that session_key is "required in practice" and to use get_sessions. The description adds no parameter meaning beyond that, so the 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?

The description states a specific verb and resource ("Fetch overtakes during F1 races") and defines the scope (on-track passes, pit-stop and penalty position changes), which is distinct from siblings like get_positions or get_laps. It does not explicitly contrast itself with any sibling, so it stops 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?

It gives a genuine availability condition ("Only available during races") and a reliability caveat, which helps the agent decide when results are meaningful. However, it names no alternative tool and offers no explicit when-to-use-vs-get_positions routing, so guidance is only implied.

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