Skip to main content
Glama
Sign In
f1verse MCP Server

f1verse MCP Server

by jinsim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Classification for any session of a weekend.

f1_session_results
Read-onlyIdempotent

Retrieve Formula 1 session results by year and round, classified for races, qualifying, sprints, or practice so position, gaps, segment times, eliminations, and best laps are clear.

Instructions

Classification for any session of a weekend. Results for one session, classified the way that kind of session actually is: races give position and gap (lapped cars as '+1 LAP'), qualifying gives per-segment times with gaps to that segment's fastest and where each driver was eliminated, practice gives a best-lap table.

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

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

A3.7/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 genuine behavioral context beyond that by explaining that the return shape varies by session type and by defining conventions such as '+1 LAP' for lapped cars and gap-to-segment-fastest for qualifying. It does not mention failure modes or what happens for a session that did not occur.

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 core payload — the three output shapes — is delivered in one well-structured sentence with a clear parallel construction (races / qualifying / practice). The opening 'classified the way that kind of session actually is' is slightly self-referential filler, but the rest earns its place.

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?

For a read-only tool with an output schema, the description doesn't need to explain return values, but it does usefully explain that returns are session-type dependent, which is the main interpretive burden here. The missing piece is how to enumerate valid session names and what happens when a requested session has no data.

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, round and session parameters are already documented in the schema, including the session name spellings and the 'Race' default. The description reinforces that session type changes output shape, which gives the session parameter meaning, but adds no syntax or format detail beyond the schema.

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 states a clear resource and scope: results for exactly one session of a weekend, plus what each session type returns (race positions/gaps with lapped cars as '+1 LAP', qualifying segment times with elimination, practice best-lap table). It is distinguishable from siblings like f1_weekend_sessions or f1_running_order in spirit, but it never names a sibling or explicitly contrasts with them.

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: an agent infers this is the tool for a specific session's classification, and the schema default of 'Race' suggests the common case. There is no explicit when-to-use, no pointer to f1_weekend_sessions for discovering valid session names, and no statement about preconditions such as data availability for older seasons.

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