Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

openf1_sessions

Retrieve Formula 1 practice, qualifying, sprint, and race sessions by season and filters, returning session keys that query other routes. Use latest to get the current or recent session.

Instructions

OpenF1 Formula 1 sessions by season and filters. Returns the practice, qualifying, sprint and race sessions OpenF1 publishes, with session type and name, start/end timestamps, meeting and circuit keys, country and location. A session_key from this list is the input to almost every other OpenF1 route; latest resolves to the current or most recent session.

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_sessions"
  }
}

Input Schema

Name	Required	Description
`year`	No	Four-digit season year; the source serves 2023 onwards example(2024)
`filter`	No	Repeatable 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: session_key, session_type, session_name, date_start, date_end, meeting_key, circuit_key, circuit_short_name, country_key, country_code, country_name, location, gmt_offset, year, is_cancelled.
`date_to`	No	Inclusive upper bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-08)
`date_from`	No	Inclusive lower bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-07)
`circuit_key`	No	Circuit key from openf1-meetings example(14)
`meeting_key`	No	Positive meeting key from openf1-meetings, or `latest` for the current meeting example(1299)
`country_code`	No	Three-letter country code example(BRA)
`country_name`	No	Country name exactly as the source reports it example(Brazil)
`is_cancelled`	No	Cancelled flag filter
`session_name`	No	Session name exactly as the source reports it example(Qualifying)
`session_type`	No	Session type; one of Practice, Qualifying, Race Enums(Practice,Qualifying,Race) example(Qualifying)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the returned field set, the fact that only sessions OpenF1 publishes are returned, and the special 'latest' resolution behavior, which is useful. It says nothing about ordering, pagination, empty-result behavior, or rate/auth constraints that an agent would need for a broad 11-parameter query surface.

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 the resource and the returned fields, then the critical session_key/latest note at the end. Almost every clause carries information; the enumeration of returned fields is slightly list-like but it substitutes for a missing output schema, so it 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?

Eleven optional parameters and no output schema make this a complex surface, and the description compensates by enumerating the returned attributes and explaining the session_key chaining behavior. The remaining gap is query semantics (default ordering, how results behave when no filters are given), which an agent would need to call it confidently.

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 schema already explains year, filter syntax, date bounds, and every enumerated attribute; the baseline of 3 applies. The description adds the meaning of 'latest' for the session-resolving parameters and frames the tool as season-plus-filter driven, but contributes no syntax or edge-case detail beyond the schema.

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 names a concrete resource (OpenF1 Formula 1 sessions) and states what the list contains: practice, qualifying, sprint and race sessions with their type, name, timestamps, meeting/circuit keys, country and location. It also signals the tool's role as the index for the rest of the OpenF1 family. It stops short of explicitly contrasting itself with motogp_sessions or any single sibling, so it is clear but not fully differentiated.

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 line 'A session_key from this list is the input to almost every other OpenF1 route' is genuine when-to-use guidance: call this first to obtain a session_key before hitting openf1_laps, openf1_weather, etc. The 'latest' note tells the agent how to get the current session without knowing a key. There is no explicit when-not / exclusion guidance, which keeps it below a 5.

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

Deploy Server