mcp-f1

Get Session Results

get_session_results

Retrieve final classification for an F1 session from OpenF1, optionally filtered by driver or position. If results return 404, retry after confirming the session is complete.

Instructions

Fetch the final classification of an F1 session from OpenF1.

Results become available a few minutes after the official results are published on the Formula 1 website. If the API returns HTTP 404, the results are not yet published for that session — retry with an earlier session_key (use get_sessions to find completed sessions).

Input Schema

TableJSON Schema

Name	Required	Description
`position`	No	int — optional, >= 1. Final position in the session.
`session_key`	No	int \| str — required in practice, positive int or 'latest'. Session identifier; use get_sessions to discover it.
`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

A3.9/5.0

Behavior4/5

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

No annotations, so the description carries the burden, and it does so well: it discloses data-availability timing (delayed a few minutes), HTTP 404 semantics, and a retry strategy. It doesn't cover auth, rate limits, or pagination, but for a read tool this is meaningful behavioral context.

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?

Front-loads the one-line purpose, then adds behavioral notes. No filler; every sentence (availability timing, 404 handling) earns its place.

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 not be explained, and the description covers purpose, availability timing, and error handling. Adequate for a 3-param read tool, though auth/permission context is absent.

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 three parameters are already documented, including session_key being required in practice and discoverable via get_sessions. The description reinforces the session_key discovery path but adds nothing about position or driver_number beyond the schema. Baseline 3 is correct.

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+resource: 'Fetch the final classification of an F1 session.' The word 'final' scopes it away from live-position tools like get_positions, giving implicit sibling differentiation, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives concrete context: results appear a few minutes after official publication, and on 404 the agent should retry with an earlier session_key. It names get_sessions as the way to find completed sessions. Missing an explicit when-not-to-use statement, but the guidance is actionable.

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