Race Calendar F1

Search F1 History

search_f1_history

Read-onlyIdempotent

Search the Formula 1 history index for drivers, teams, circuits, and races with bounded, cursor-based results.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results to return. Defaults to 10 and never exceeds 20.
`query`	Yes	Driver, team, circuit, or race text to find.
`types`	No	Optional unique entity types to include in the search.
`cursor`	No	Opaque continuation cursor returned by an earlier history search.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`query`	Yes
`types`	Yes
`nextCursor`	Yes
`generatedAt`	Yes
`sourceUpdatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

removedOutput schema / properties / nextCursor / anyOf

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

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

removedOutput schema / properties / sourceUpdatedAt / anyOf

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

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

Changed7 schema fields changedJul 31, 2026

addedInput schema / $schema

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

addedInput schema / description

Added value: +"Search the bounded Formula 1 history index."

addedInput schema / properties / cursor / description

Added value: +"Opaque continuation cursor returned by an earlier history search."

addedInput schema / properties / limit / description

Added value: +"Maximum results to return. Defaults to 10 and never exceeds 20."

addedInput schema / properties / types / description

Added value: +"Optional unique entity types to include in the search."

addedOutput schema / $schema

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

addedOutput schema / description

Added value: +"Bounded cursor page of matching Formula 1 drivers, teams, circuits, and races."

AddedJul 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations by mentioning 'bounded, cursor-based results,' which signals pagination and result limits. It does not detail edge cases such as empty results or cursor expiration, but the core behavior is transparent.

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?

A single front-loaded sentence conveys the action, resource, scope, and a key behavioral trait (bounded cursor-based results). There is no filler, repetition, or extraneous detail; every word 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 4-parameter search tool with full schema descriptions, a rich output schema, and annotations covering safety, the description covers the essential scoping and pagination behavior. The only notable omission is explicit guidance on choosing this tool over specific getter siblings, which is more of a usage-guideline gap.

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%, and every parameter already has a clear description, including default/max for limit, allowed values for types, and the opaque cursor semantics. The description's mention of 'drivers, teams, circuits, and races' mirrors the types enum rather than adding new meaning, so the value-added is minimal.

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 names a specific action ('Search'), a specific resource ('the Formula 1 history index'), and a clear scope ('drivers, teams, circuits, and races'). The phrase 'bounded, cursor-based results' also distinguishes it from sibling tools that retrieve specific entities rather than performing a search.

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?

The description implies when to use the tool: when searching broadly across the history index. However, it does not explicitly state when not to use it or name alternatives like get_f1_circuit or get_f1_historical_race_result for direct lookups. The usage context is inferable but not spelled out.

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?