f1verse MCP Server

Overview Schema Source Related Servers Discussions Admin

Where the season stands right now and what is next.

f1_season_status

Read-onlyIdempotent

Reports where the season stands: last completed race to the next session, with hours until it starts. Use it to answer when the next race is or to resolve the last race to a round number.

Instructions

Where the season stands right now and what is next. The latest completed race, sessions that have finished and settled, the next session and how many hours until it starts. Use this to answer 'when is the next race' or to resolve 'the last race' into a concrete round number before calling the other tools.

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

Input Schema

Name	Required	Description	Default
`year`	Yes	Season year, e.g. 2026. Race data 2023+.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.15.0Nov 9, 2026

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.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful behavioral context beyond that: 'right now' signals a time-sensitive snapshot, and 'finished and settled' warns that completed sessions may lag in availability. Return-shape detail is partly redundant given the output schema, which keeps it from a 5.

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?

Three tight sentences, front-loaded with the purpose, then contents, then usage. The opening sentence largely restates the title, which is mild redundancy, but nothing else is wasted.

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?

With an output schema present the description needn't document return values, and the one parameter is fully covered by the schema. What remains slightly under-specified is freshness — how 'right now' is computed and how stale the data can be — but nothing essential for correct invocation is missing.

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?

There is a single parameter with 100% schema description coverage, including the 2023+ data note, so the schema carries the semantics. The description never mentions the year argument or how out-of-range years behave, so it adds nothing on top — baseline 3.

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?

The description names the specific resource and enumerates its content: the latest completed race, sessions that have finished and settled, and the next session with an hours-until countdown. That level of specificity lets an agent separate it from siblings like f1_weekend_sessions or f1_race_events without opening any 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?

It gives concrete when-to-use triggers ('when is the next race', resolving 'the last race' into a round number) and even a sequencing hint that it should be called before other tools. It falls short of a 5 because it names no sibling alternatives and states no conditions under which not to use it.

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