Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

openf1_meetings

Retrieve Formula 1 Grand Prix and testing weekends for a season, filtered by country, circuit, location, or dates, to discover the meeting and circuit values other F1 resources filter on.

Instructions

OpenF1 Formula 1 meetings by season and filters. Returns Formula 1 Grand Prix and testing weekends from OpenF1's anonymous public API: meeting and official name, country, circuit key and type, circuit info/image URLs, GMT offset and start/end timestamps. A season query is the discovery surface for the country, circuit and meeting values the other OpenF1 resources filter on.

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

NameRequiredDescriptionDefault
yearNoFour-digit season year; the source serves 2023 onwards example(2024)
filterNoRepeatable upstream filter written as <attribute><operator><value>, with operators >=, <=, =, > and <. Repeated filters on the same attribute are OR'ed, a lower and upper bound form an inclusive range, and different attributes are AND'ed. Filterable attributes on this route: meeting_key, meeting_name, meeting_official_name, location, country_key, country_code, country_name, country_flag, circuit_key, circuit_short_name, circuit_type, circuit_info_url, circuit_image, gmt_offset, date_start, date_end, year, is_cancelled.
date_toNoInclusive upper bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-08)
locationNoCity or geographical location of the meeting example(São Paulo)
date_fromNoInclusive lower bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-07)
circuit_keyNoCircuit key from openf1-meetings example(14)
circuit_typeNoCircuit type, one of Permanent, Temporary - Road, Temporary - Street
country_codeNoThree-letter country code example(BRA)
country_nameNoCountry name exactly as the source reports it example(Brazil)
is_cancelledNoCancelled flag filter
meeting_nameNoMeeting name exactly as the source reports it example(Singapore Grand Prix)
circuit_short_nameNoCircuit short name example(Interlagos)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose valuable behavior: the data comes from an 'anonymous public API' (implying no auth), and it lists the returned fields including circuit info/image URLs and GMT offset and start/end timestamps. However, it omits pagination, ordering, rate limits, and coverage limits (the 2023-onwards constraint only appears in the schema, not the description).

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, then return contents, then the discovery role. Every sentence carries information, though the return-field enumeration is somewhat long relative to the little guidance it adds.

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 12-parameter read tool with no annotations and no output schema, the description covers purpose, return contents, data source, and how it relates to other OpenF1 resources. Gaps remain around pagination/ordering and coverage limits, but the schema handles parameters thoroughly.

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 each of the 12 parameters, including the repeatable filter grammar and its operators, already fully documented in the schema. The description only restates that filtering is by season and filters, adding no syntax, format, or interaction semantics beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('OpenF1 Formula 1 meetings by season and filters') and enumerates what a result contains (meeting/official name, country, circuit key and type, URLs, GMT offset, timestamps). It also distinguishes this route conceptually by saying it is 'the discovery surface for the country, circuit and meeting values the other OpenF1 resources filter on', though it never names a concrete sibling alternative.

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 line about being the 'discovery surface' for filter values implies a when-to-use context (call this first to learn valid country/circuit/meeting values), but there is no explicit when-not guidance and no named alternative among siblings like openf1_sessions or formula1_meetings. Usage is inferable rather than stated.

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

Deploy Server

Other Tools