f1verse MCP Server

Overview Schema Source Related Servers Discussions Admin

A driver's career totals, 1950 to today.

f1_driver_career

Read-onlyIdempotent

Retrieve a Formula 1 driver's career totals—starts, wins, podiums, poles, and points from 1950 to today—plus upcoming round-number milestones.

Instructions

A driver's career totals, 1950 to today. Starts, wins, podiums, poles and points for one driver across all of F1 history, plus the next round-number milestones they are approaching. Takes an Ergast-style driver id such as 'max_verstappen', 'hamilton' or 'leclerc'.

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": {
      "driver_id": "<driver_id>"
    },
    "name": "f1_driver_career"
  }
}

Input Schema

Name	Required	Description	Default
`driver_id`	Yes	Ergast/Jolpica driver id, e.g. 'max_verstappen', 'hamilton'.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.15.0Nov 9, 2026

changedOutput schema / (root)

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

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructiveness, so the safety profile is fully covered. The description adds useful scope detail (full history 1950–today, includes milestone projections) but says nothing about edge cases like an unknown driver id or the absence of pre-1950 data.

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 short sentences, front-loaded with the scope and followed by the returned metrics and the parameter format. Little waste, though the first sentence duplicates the title verbatim and the metric list partly overlaps what the output schema already conveys.

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?

For a single-parameter read tool with a full output schema and rich annotations, the description supplies everything an agent needs: what period is covered, what metrics come back, the extra milestone content, and the expected id format.

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?

With one parameter at 100% schema description coverage, the schema already defines driver_id and even supplies the same style of examples. The description's 'Ergast-style driver id' phrasing and examples largely restate the schema, adding no format rules or fallback behavior for alternate id styles.

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 resource and scope: career totals for one driver from 1950 to today, enumerating the metrics returned (starts, wins, podiums, poles, points) plus approaching milestones. No sibling tool in the list offers career aggregates, so an agent can distinguish it without opening the schema.

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 only implied by the phrasing 'for one driver across all of F1 history' – a career-stats lookup. There is no explicit guidance on when to choose this over related siblings such as f1_standings, f1_season_status or f1_season_shape, nor any prerequisite or exclusion stated.

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