Race Calendar F1

Live F1 Session Status

get_f1_live_session

Read-onlyIdempotent

Get the latest explicitly timestamped status for the current or selected Formula 1 session. Returns unavailable rather than implying stale data is live.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Season to inspect. Defaults to the current UTC season.
`meetingKey`	No	Optional OpenF1 meeting key. Omit to discover the current live session.
`sessionKey`	No	Optional OpenF1 session key. Requires meetingKey when supplied.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`state`	Yes
`isLive`	Yes
`endDate`	Yes
`message`	Yes
`sourceUrl`	Yes
`startDate`	Yes
`meetingKey`	Yes
`observedAt`	Yes
`sessionKey`	Yes
`sessionKind`	Yes
`sessionName`	Yes
`dataTimestamp`	Yes
`dataDelaySeconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 22, 2026

removedOutput schema / properties / dataTimestamp / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / dataTimestamp / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / endDate / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / endDate / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / message / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / message / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / sessionName / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / sessionName / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / startDate / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / startDate / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedAug 1, 2026
- removedInput schema / dependentRequired
```
Removed value: -{
-  "sessionKey": [
-    "meetingKey"
-  ]
-}
```

Changed4 schema fields changedJul 31, 2026

addedInput schema / $schema

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

addedInput schema / description

Added value: +"Inspect the current Formula 1 session or select one 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: +"Explicitly timestamped Formula 1 session state with data freshness and availability context."

AddedJul 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive behavior. The description adds valuable context beyond that: results are explicitly timestamped and the tool returns 'unavailable' rather than presenting stale data as live, which is meaningful behavioral disclosure.

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?

Two sentences carry all necessary information with no fluff. The core behavior is front-loaded and the stale-data handling is conveyed efficiently.

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?

Given the output schema, complete parameter descriptions, and annotations covering safety, the description is sufficient for an agent to select and call this tool correctly. No essential behavioral or selection information is missing.

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 meaningfully documented. The description adds no parameter-specific detail, so the baseline score of 3 applies.

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 clear verb and resource: retrieving the latest explicitly timestamped status for a current or selected F1 session. It distinguishes itself from historical/results siblings by emphasizing live status and stale-data semantics.

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 clearly indicates this is for current or selected sessions, and the schema adds practical guidance such as omitting meetingKey to discover the live session and requiring meetingKey with sessionKey. It does not explicitly name sibling alternatives or exclusions, but the intended context is clear.

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?