Skip to main content
Glama
Sign In
f1verse MCP Server

f1verse MCP Server

by jinsim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Lap times the stewards struck out, with reinstatements.

f1_deleted_laps
Read-onlyIdempotent

Retrieve every steward-deleted lap time from a session, including the car, time, reason, and reinstatement status, so you can verify fastest laps and qualifying results before relying on them.

Instructions

Lap times the stewards struck out, with reinstatements. Every lap-time deletion race control announced in a session, with the car, the time, the stated reason, and whether the deletion still stands — a reinstated lap is reported with the reversal visible rather than silently dropped. Use before treating a fastest lap or a qualifying position as settled.

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

Input Schema

NameRequiredDescriptionDefault
yearYesSeason year, e.g. 2026. Race data 2023+.
roundYesRound number within the season, 1-based.
sessionNoSession name as the calendar spells it: Race, Qualifying, Sprint, Sprint Qualifying, Practice 1-3. Defaults to Race.Race

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.0
    • 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"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds genuine value by disclosing how reinstatements are modeled (reported with the reversal visible rather than dropped) and that the set is every announced deletion in a session. It says nothing about ordering, volume, or how deleted times relate to entries in session results, leaving gaps the schema and annotations do not fill.

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 sentences, front-loaded with the resource and scoped by the use case; the second sentence lists the returned fields efficiently. The first sentence merely restates the title verbatim, a small redundancy that keeps it from a top score.

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?

A read-only lookup tool with an output schema, full parameter documentation, and rich annotations needs only purpose, contents, and a use trigger — all present. An agent knows when to call it and what the response will contain without further description.

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%, so year, round, and session are fully documented including the default, and the description adds little parameter-level meaning beyond the phrase "in a session." Baseline 3 applies when the schema carries parameter semantics.

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?

Names a concrete resource (deleted lap times) plus a distinguishing attribute (reinstatements) and states the record contents: car, time, reason, and whether the deletion still stands. No sibling tool covers stewards' deletions, so an agent can route here unambiguously.

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?

"Use before treating a fastest lap or a qualifying position as settled" gives a concrete decision point that implies the alternative (relying on session results/standings). It stops short of naming a sibling or stating when the tool is unnecessary, but the triggering context is explicit.

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

Deploy Server

Other Tools