Race Calendar F1

Recent F1 Changes

get_f1_updates

Read-onlyIdempotent

Get recent public schedule, standings, and result changes after an optional timestamp or cursor.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum changes to return. Defaults to 20 and never exceeds 50.
`since`	No	Only return changes after this UTC timestamp.
`cursor`	No	Opaque continuation cursor returned by an earlier updates request.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`since`	Yes
`nextCursor`	Yes
`generatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 22, 2026

changedInput schema / properties / since / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

removedOutput schema / properties / nextCursor / anyOf

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

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

removedOutput schema / properties / since / anyOf

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

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

Changed6 schema fields changedJul 31, 2026

addedInput schema / $schema

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

addedInput schema / description

Added value: +"Read a bounded page of recent public Formula 1 changes."

addedInput schema / properties / cursor / description

Added value: +"Opaque continuation cursor returned by an earlier updates request."

addedInput schema / properties / limit / description

Added value: +"Maximum changes to return. Defaults to 20 and never exceeds 50."

addedOutput schema / $schema

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

addedOutput schema / description

Added value: +"Bounded cursor page of recent public Formula 1 schedule, standings, and result changes."

AddedJul 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by noting the data is public and that results are change-oriented with timestamp/cursor-based incremental behavior. It does not mention rate limits or auth, but the public/read-only framing reduces the need.

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 description is a single sentence with the main purpose front-loaded and the optional filter mechanism at the end. It contains no filler or redundant restatement of the title.

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?

With a full output schema, complete parameter descriptions, and protective annotations, the description provides enough context for correct invocation. The only minor gap is not explaining whether since and cursor may be combined, but the schema's cursor description implies it is a continuation from an earlier request.

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%: limit, since, and cursor all have individual descriptions. The description only restates that the timestamp/cursor are optional, adding no semantic meaning beyond the schema. Baseline 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 uses a specific verb, 'Get', and names the resource: 'recent public schedule, standings, and result changes' plus the optional timestamp/cursor scope. This clearly differentiates it from sibling snapshot tools like get_f1_standings and get_f1_season_schedule.

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 phrasing 'recent ... changes after an optional timestamp or cursor' clearly implies this is the delta/incremental-update tool, as opposed to full-state sibling tools. It does not explicitly name alternatives or give when-not-to-use conditions, but the context is strong enough for an agent to route correctly.

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?