Race Calendar F1

F1 Session Results

get_f1_session_results

Read-onlyIdempotent

Get the published F1DB classification for one Formula 1 session by season, meeting key, and session key, with positions and available result details.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	Yes	Formula 1 season year.
`meetingKey`	Yes	OpenF1 meeting key for the race weekend.
`sessionKey`	Yes	OpenF1 session key.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`source`	Yes
`results`	Yes
`sourceUrl`	Yes
`meetingKey`	Yes
`sessionKey`	Yes
`resultCount`	Yes
`canonicalUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 22, 2026
- removedOutput schema / properties / results / items / properties / constructorName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / constructorName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / driverName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / driverName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / duration / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / duration / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / gapToLeader / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / gapToLeader / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / headshotUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / headshotUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / points / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / points / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / results / items / properties / positionLabel / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / positionLabel / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed4 schema fields changedAug 5, 2026

addedOutput schema / properties / results / items / properties / positionLabel

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "driverNumber",
-  "driverName",
-  "headshotUrl",
-  "constructorName",
-  "position",
-  "numberOfLaps",
-  "points",
-  "duration",
-  "gapToLeader",
-  "status"
-]New value: +[
+  "driverNumber",
+  "driverName",
+  "headshotUrl",
+  "constructorName",
+  "position",
+  "positionLabel",
+  "numberOfLaps",
+  "points",
+  "duration",
+  "gapToLeader",
+  "status"
+]

addedOutput schema / properties / source

Added value: +{
+  "const": "F1DB",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "year",
-  "meetingKey",
-  "sessionKey",
-  "canonicalUrl",
-  "sourceUrl",
-  "resultCount",
-  "results"
-]New value: +[
+  "year",
+  "meetingKey",
+  "sessionKey",
+  "canonicalUrl",
+  "sourceUrl",
+  "source",
+  "resultCount",
+  "results"
+]

Changed4 schema fields changedJul 31, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / description

Added value: +"Select one Formula 1 session by season, meeting key, and session key."

addedOutput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / description

Added value: +"Published Formula 1 session classification with source and canonical links."

AddedJul 24, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description's 'Get' is consistent. It adds the 'published F1DB classification' qualifier, implying stable/published data rather than live results. No contradictions or additional behavioral details (rate limits, auth, pagination) are provided.

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?

Single sentence, front-loaded with the action and resource, and every phrase earns its place. No filler or redundancy.

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 simple three-key lookup with full schema coverage, an output schema, and safe read-only/idempotent annotations, the description provides everything needed to invoke it. Missing context like how to discover the keys is external, not a gap in the definition.

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% – year, meetingKey, and sessionKey each have descriptive text. The description repeats the three keys but adds no syntax, format, or relationship detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Get') and resource ('published F1DB classification for one Formula 1 session'), and identifies the selection keys (season, meeting key, session key). It does not explicitly contrast with sibling tools like get_f1_race_classification or get_f1_starting_grid, but the session-specific scope is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to prefer this tool over siblings; no exclusions or alternatives are mentioned. The key-based lookup is an implicit trigger, but the description does not state when this should be used versus get_f1_race_classification or get_f1_live_session.

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

All Race Calendar F1 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?