f1verse MCP Server

Overview Schema Source Related Servers Discussions Admin

Evidence-linked race and pit-cycle events.

f1_race_events

Read-onlyIdempotent

Retrieve evidence-linked Formula 1 race and pit-cycle events with stable IDs, input lineage, and observed gap changes for race analysis.

Instructions

Evidence-linked race and pit-cycle events. Stable event IDs, input lineage and observed gap changes. No causal strategy claim or media download.

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_events"
  }
}

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.

Addedv0.15.0Nov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations by disclosing stable event IDs, input lineage, observed gap changes, and explicit non-goals around causal claims and media downloads.

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?

The description is short and front-loaded, with each sentence contributing scope or boundary information. The first sentence largely restates the title, which is a minor redundancy but not harmful.

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 the description need not explain return values in detail. Given the rich annotations and complete parameter schema, the description is nearly complete, though it could better clarify when this tool should be used instead of related F1 event or analysis tools.

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 the year and round parameters are already well documented in the input schema. The description does not add parameter-specific meaning beyond what the schema provides, which is acceptable at baseline.

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 identifies a specific resource: evidence-linked race and pit-cycle events, with stable event IDs, input lineage, and observed gap changes. It is clear what the tool returns, but it does not explicitly differentiate itself from siblings such as f1_turning_points or f1_pace_changes.

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?

Usage is implied by the event-focused purpose, and the description adds a negative boundary by excluding causal strategy claims and media downloads. However, it does not state when to choose this tool over related siblings or name any alternatives.

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