f1verse MCP Server

Overview Schema Source Related Servers Discussions Admin

Everything that happened in one race, as structured JSON.

f1_race_story

Read-onlyIdempotent

Retrieve a complete Formula 1 race summary as structured JSON in one call, including results, lead changes, laps led, timeline, tyre stints, median pace, and safety-car periods.

Instructions

Everything that happened in one race, as structured JSON. The whole race in one call: final results with broadcast-convention gaps, lead changes, laps led per driver, the event timeline, tyre stints, median race pace (pit/SC/VSC laps excluded), and safety-car interruptions. Use this first for any 'what happened in race X' question — it is one request instead of six.

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>",
      "round": "<round>"
    },
    "name": "f1_race_story"
  }
}

Input Schema

Name	Required	Description	Default
`year`	Yes	Season year, e.g. 2026. Race data 2023+.
`round`	Yes	Round number within the season, 1-based.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.15.0Nov 9, 2026

addedInput schema / properties / round / minimum
```
Added value: +1
```
addedInput schema / properties / year / minimum
```
Added value: +1950
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedv0.1.0Nov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description rightly spends its words elsewhere: it discloses payload composition and a real computational caveat ('median race pace (pit/SC/VSC laps excluded)') that an agent could not infer from the schema. It adds no cost/latency or data-freshness notes beyond the implicit 'one request instead of six' hint.

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 sentences, front-loaded with the resource and scope, then a dense contents list, then the call-to-action. Every clause carries information; the only mild redundancy is that the opening line restates the title.

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 still usefully enumerates what the aggregate contains. For a two-parameter read tool this is close to complete; the only shortfall is the absence of guidance on when the aggregate is too coarse and a narrower sibling is warranted.

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 coverage is 100% with both parameters documented (including the 'Race data 2023+' constraint on year), so the schema carries parameter meaning. The description adds nothing parameter-specific beyond the phrase 'race X', which is the baseline expectation here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('everything that happened in one race') and then enumerates the payload contents — results, lead changes, laps led, timeline, stints, median pace, safety cars. That enumeration, plus the 'one request instead of six' framing, lets an agent distinguish it from aggregation-adjacent siblings like f1_race_events or f1_turning_points without opening a schema.

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 explicit routing guidance: 'Use this first for any "what happened in race X" question', with a concrete efficiency rationale. It does not state when to prefer a narrower sibling (e.g. a single-event timeline or a quick brief), so the exclusion half of the guidance is missing.

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