Race Calendar F1

F1 Starting Grid

get_f1_starting_grid

Read-onlyIdempotent

Get the published F1DB starting grid for one Formula 1 session by season, meeting key, and session key; use session results for the final classification.

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
`sourceUrl`	Yes
`entryCount`	Yes
`meetingKey`	Yes
`sessionKey`	Yes
`canonicalUrl`	Yes
`startingGrid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 22, 2026
- removedOutput schema / properties / startingGrid / items / properties / constructorName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / startingGrid / items / properties / constructorName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / startingGrid / items / properties / driverName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / startingGrid / items / properties / driverName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / startingGrid / items / properties / headshotUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / startingGrid / items / properties / headshotUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / startingGrid / items / properties / lapDuration / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / startingGrid / items / properties / lapDuration / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedAug 5, 2026

addedOutput schema / properties / source

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

changedOutput schema / required

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

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 starting grid with source and canonical links."

AddedJul 24, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds useful context that the data is the 'published' starting grid rather than live or provisional, but it does not disclose behaviors such as missing grids for unpublished sessions or error cases. This is adequate but not rich.

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 entire description is one tightly packed sentence that front-loads the main action and resource, then adds a useful scoping caveat. There is no filler or redundant restatement of structured fields.

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 read-only lookup tool with three fully documented parameters, a safety profile in annotations, and an output schema, the description covers the essential invocation context. It says what is returned (starting grid), how to select the session, and where to go for the final classification.

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%, with all three parameters (year, meetingKey, sessionKey) individually documented. The description restates these keys in prose but adds no additional semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 verb and resource: 'Get the published F1DB starting grid for one Formula 1 session.' It clearly distinguishes this tool from sibling result/classification tools by emphasizing 'starting grid' and by noting that final classification belongs to session results.

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?

The description provides an explicit usage directive: 'use session results for the final classification.' This tells the agent when to prefer a different tool, although it does not enumerate broader conditions or alternative tools beyond that one case.

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?