mcp-f1

Get Teams Championship

get_teams_championship

Fetch Formula 1 teams' championship standings for a race session from OpenF1. Provide session_key (or 'latest') and optional team_name to retrieve specific team standings.

Instructions

Fetch teams championship standings from OpenF1 (beta endpoint).

Only available for race sessions. This endpoint is in beta: its behavior or fields may change without notice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`team_name`	No	str — optional, 1-100 chars, e.g., 'McLaren'.
`session_key`	No	int \| str — required in practice, positive int or 'latest'. Race session identifier; use get_sessions with session_type='Race' to discover it.

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

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the beta status and that fields may change without notice, plus the race-session-only restriction, but says nothing about auth, rate limits, or pagination behavior.

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, zero waste, with the primary purpose front-loaded and the caveats (race-only, beta) following in order of importance.

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 described. The description covers the key operational caveats (session type restriction, beta instability) an agent needs; only cross-tool routing guidance 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%, and both parameters (team_name, session_key) are already documented in the schema including the 'latest' option and how to discover session_key. 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?

States a specific verb (fetch) and resource (teams championship standings) from a named source (OpenF1), which cleanly separates it from the sibling get_drivers_championship. It does not explicitly name that sibling, so differentiation is implied by the word 'teams' rather than stated.

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?

'Only available for race sessions' gives a concrete when-to-use constraint that rules out practice/qualifying sessions. It stops short of naming an alternative or explaining what to do for non-race sessions, so it is clear context without explicit alternatives.

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