Race Calendar F1

F1 Circuit Details

get_f1_circuit

Read-onlyIdempotent

Get circuit metadata and normalized track geometry for a race weekend selected by meeting key, round, race name, or slug.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Race Calendar race slug, such as round-6-miami-grand-prix or miami-grand-prix.
`year`	Yes	Formula 1 season year.
`round`	No	Championship round number for the season.
`raceName`	No	Human-friendly Grand Prix or race name, matched case-insensitively.
`meetingKey`	No	OpenF1 meeting key for the race weekend.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`round`	Yes
`circuit`	Yes
`raceName`	Yes
`sourceUrl`	Yes
`meetingKey`	Yes
`canonicalUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 22, 2026
- removedOutput schema / properties / circuit / properties / countryCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / circuit / properties / countryCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / circuit / properties / imageUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / circuit / properties / imageUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / circuit / properties / type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / circuit / properties / type / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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 race weekend by season and exactly one of meetingKey, round, raceName, or slug."

addedOutput schema / $schema

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

addedOutput schema / description

Added value: +"Formula 1 circuit identity, venue metadata, normalized geometry, 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 covered. The description adds only functional context ('normalized track geometry') and does not disclose extra behavioral traits such as error handling, data source, or output conventions, though the output schema helps fill that gap.

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, front-loaded sentence with no filler. Every phrase earns its place by conveying the resource, the purpose, and the selection mechanism without 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?

Given the rich input schema, full schema description coverage, output schema presence, and safety-related annotations, the description is sufficient for correct tool invocation. It identifies what is returned, how the race weekend is selected, and leaves parameter details to the schema where they already live.

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%, so the input schema already documents every parameter including selector alternatives and constraints. The description names the selector types but adds no meaning beyond what the schema provides, so a baseline score 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 circuit metadata and normalized track geometry'. It also specifies the selection scope ('race weekend selected by meeting key, round, race name, or slug'), making it clearly distinct from sibling tools that cover race results, standings, or session data.

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 situates the tool as the way to obtain circuit metadata/track geometry for a race weekend, and the schema reinforces that exactly one selector must be used. It does not explicitly name alternatives or exclusion conditions, but the context is clear enough for an agent to choose this tool over the listed siblings.

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?