Skip to main content
Glama
Sign In
OpenF1 MCP Server

OpenF1 MCP Server

by ragulhari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Overtakes

get_overtakes
Read-onlyIdempotent

Retrieve Formula 1 overtakes and position changes between drivers, including on-track passes, pit stops, and penalties, with filters by session, driver, date, and position.

Instructions

Position exchanges between two drivers in a race (on track, pit stops or penalties). Data can be incomplete.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return (default 200, max 1000). A summary is added when the result is larger.
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: date, meeting_key, overtaken_driver_number, overtaking_driver_number, position, session_key. Array fields cannot be filtered.
positionNoPosition of the overtaking driver after the overtake.
date_fromNoStart of the time range (UTC, ISO 8601), e.g. "2025-11-09T17:05:00Z". Filters on "date" >= value.
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.
overtaken_driver_numberNoDriver who was overtaken.
overtaking_driver_numberNoDriver who made the overtake.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds meaningful behavioral context by warning that data can be incomplete and by clarifying which race events count as overtakes.

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?

The description is front-loaded and compact: one sentence defines the resource and the second sentence adds a critical data-quality caveat. There is no wasted text.

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?

The description is adequate given rich annotations and complete schema parameter coverage, but it is sparse for a ten-parameter query tool. It does not explain return shape or recommend scoping by meeting/session/date, though the schema partially 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 all ten parameters are already well documented in the schema. The description adds no parameter-specific meaning beyond that, which matches the baseline for high 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 position exchanges between two drivers, including on-track, pit-stop, and penalty cases. It is more specific than the tool name alone, but it does not explicitly distinguish itself from nearby siblings such as get_position or get_intervals.

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?

There is no explicit guidance on when to use this tool versus alternatives like get_position, get_intervals, or get_laps. The phrase 'in a race' implies scoping, but no when/when-not conditions or recommended filters are stated.

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