Crawlora MCP

openf1_meetings

Read-only

List Formula 1 meetings (Grand Prix and testing weekends) for a season, returning meeting keys, names, country, circuit keys and start/end dates. Use year 2023 or later, or other filters; this is the discovery step that yields the meeting_key the session-scoped OpenF1 tools take. A valid empty filter match returns count 0 with an empty list, and an anonymous call during a live session returns 503. For finer queries, add repeatable filter= (operators >=, <=, =, >, <) to narrow by year or country_name, e.g. filter=year=2026; repeated filters on one attribute are OR'ed and ranges are inclusive.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "openf1_meetings"
  }
}

Input Schema

Name	Required	Description
`year`	No	Optional four-digit season year; the source currently serves 2023 onwards.
`filter`	No	Repeatable upstream filter expression written as <attribute><operator><value> with operators >=, <=, =, > and <. Repeated filters on the same attribute are OR'ed, ranges are inclusive, and unknown attributes or values are rejected before the upstream call.
`date_to`	No	Optional meeting end upper bound; RFC3339 or YYYY-MM-DD.
`location`	No	Optional city or geographical location of the meeting.
`date_from`	No	Optional meeting start lower bound; RFC3339 or YYYY-MM-DD.
`circuit_key`	No	Optional circuit key from the meetings list.
`circuit_type`	No	Optional circuit type. Values: Permanent, Temporary - Road, Temporary - Street.
`country_code`	No	Optional three-letter country code such as BRN.
`country_name`	No	Optional country name exactly as the meetings list reports it.
`is_cancelled`	No	Optional cancelled flag filter.
`meeting_name`	No	Optional meeting name such as Singapore Grand Prix.
`circuit_short_name`	No	Optional circuit short name such as Interlagos.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnlyHint/openWorldHint annotations: an empty-but-valid match returns count 0 with an empty list rather than an error, an anonymous call during a live session returns 503, unknown attributes or values are rejected before the upstream call, repeated filters on one attribute are OR'ed, and ranges are inclusive. These are the failure modes an agent needs to plan around, none of which appear in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose and where it fits, then edge cases, then filter syntax. Dense but each sentence carries real information. The final sentence is long and packs multiple rules, but none of it is filler.

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 12-parameter, zero-required discovery tool with a full output schema and complete annotation coverage, the description supplies the things structured fields cannot: the discovery-role framing, the empty-result contract, the 503 auth condition, and the filter grammar. Return-value detail is rightly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description earns above baseline by explaining the repeatable filter syntax that the schema only gestures at: the <attribute><operator><value> form, the allowed operators, OR semantics across repeats, inclusive ranges, and pre-call rejection of unknown attributes/values.

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?

States a specific verb (list) and resource (Formula 1 meetings, i.e. Grand Prix and testing weekends), enumerates the returned fields (meeting keys, names, country, circuit keys, start/end dates), and explicitly frames itself as the discovery step that produces the meeting_key other OpenF1 tools consume. An agent can tell what this returns and where it sits in the tool chain without opening the schema.

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?

Gives concrete usage context: use year 2023 or later or other filters, and use this as the discovery step before session-scoped calls. It also gives a fallback path with the filter expression for finer narrowing. It does not name a specific alternative sibling (e.g. a narrower sessions lookup) as an exclusion, so it falls just short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP 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?