Pitwall F1

Overview Schema Source Related Servers Discussions Admin

Race Results (FastF1)

get_race_results

Read-onlyIdempotent

Retrieves final Formula 1 race results by year and Grand Prix, returning position, driver, team, and points for each entry.

Instructions

Get the final classification (Position, Driver, Team, Points).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "gp": "<gp>"
    },
    "name": "get_race_results"
  }
}

Input Schema

Name	Required	Description	Default
`gp`	Yes
`year`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 28, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the tool returns the final classification with specific fields, which gives some context, but does not disclose any additional behavioral traits like data source freshness or error conditions. With annotations doing heavy lifting, a 3 is appropriate.

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?

A single, front-loaded sentence with no wasted words. It is efficiently structured, though its extreme brevity leaves it under-specified rather than overly verbose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While an output schema exists and annotations cover safety, the description omits any explanation of the required input parameters and any usage context. For a two-parameter tool with 0% schema coverage, this leaves the agent without enough information to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not mention the required parameters year or gp at all. It provides no meaning, format, or constraints for these parameters, failing to compensate for the schema gap.

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 and resource: 'Get the final classification' with listed fields, which is clear. However, it does not differentiate from sibling tools such as get_sprint_results, get_historical_results, or get_qualifying_progression, leaving ambiguity about when this exact result set applies.

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?

Provides no guidance on when to use this tool versus alternatives like get_historical_results or get_sprint_results, nor any prerequisites or exclusions. The phrase 'final classification' implies post-race use, but this is not made explicit.

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

Deploy Server