f1verse MCP Server

Overview Schema Source Related Servers Discussions Admin

Observed retirement survival across selected settled races.

f1_retirement_risk

Read-onlyIdempotent

Analyze observed retirement survival across selected F1 races with all-cause Kaplan-Meier curves over completed laps, censoring finishes; not a calibrated future reliability forecast.

Instructions

Observed retirement survival across selected settled races. All-cause Kaplan-Meier over completed laps. Finishes are censored. Not a calibrated future reliability forecast; causes are unavailable.

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

Input Schema

Name	Required	Description	Default
`year`	Yes	Season year, e.g. 2026. Race data 2023+.
`rounds`	Yes	Up to ten rounds to pool; repeated rounds deduplicated.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.15.0Nov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses the statistical method, censoring treatment, and key limitations: it is not a calibrated future reliability forecast and causes are unavailable. This is meaningful behavioral context for interpreting the output.

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?

The description is four short sentences, front-loaded with the core purpose and followed by method and caveats. Every sentence adds useful information without repetition.

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

Completeness5/5

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

Given the output schema, rich annotations, and full parameter schema coverage, the description is complete enough for an agent to understand the analysis and its limitations. It does not need to explain return values because an output schema exists.

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 schema already documents year and rounds, including the 2023+ data note and deduplication behavior. The description adds no parameter-specific meaning beyond the schema.

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 states a specific analysis: observed retirement survival across selected settled races, using all-cause Kaplan-Meier over completed laps with censored finishes. This clearly distinguishes it from sibling tools such as race events, results, or 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for use: selected settled races, completed laps, and observed survival rather than a calibrated future reliability forecast. It also states a when-not condition, but it does not name alternative sibling tools for related questions.

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