Skip to main content
Glama
Sign In
OpenF1 MCP Server

OpenF1 MCP Server

by ragulhari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Drivers championship (beta)

get_championship_drivers
Read-onlyIdempotent

Retrieve Formula 1 drivers' championship points and positions before and after a race to compare standings changes. Filter race sessions by meeting or driver number.

Instructions

Drivers championship points and position before and after a race. Race sessions only.

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.
filtersNoExtra comparison filters, e.g. [{"field":"lap_duration","op":"<","value":90}]. Allowed fields: driver_number, meeting_key, points_current, points_start, position_current, position_start, session_key. Array fields cannot be filtered.
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.
driver_numberNoDriver number(s) for the season, e.g. 1, 44, 81. Give a list to get more than one driver.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a safe, idempotent, read-only operation. The description adds the race-session-only constraint and clarifies that values are shown before and after a race, but it does not explain pagination, beta behavior, or output structure beyond the basic resource.

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?

Two short sentences with the core purpose front-loaded and no wasted text. The session-type restriction is stated directly after the main description.

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?

With full schema coverage, read-only annotations, and no output schema, the description adequately covers what the tool returns and its key constraint. It stops short of explaining return shape or beta caveats, but nothing critical for invocation is missing.

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 six parameters are fully documented in the input schema. The description adds no parameter-specific information beyond what the schema already provides.

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 states the resource (drivers championship points and positions) and the temporal scope (before and after a race). It does not explicitly contrast itself with sibling tools such as get_championship_teams, though the 'Drivers' qualifier implicitly distinguishes it.

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 'Race sessions only' gives a useful usage constraint, excluding non-race sessions. However, it does not name alternatives or specify when to prefer this tool over related ones like get_session_result or get_championship_teams.

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