Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

openf1_laps

Retrieves per-lap Formula 1 data such as lap and sector durations, speed-trap and intermediate speeds, and pit-out flags. Pass session_key and driver_number to keep responses bounded.

Instructions

OpenF1 Formula 1 lap times and sectors. Returns per-lap data: lap duration, three sector durations, intermediate and speed-trap speeds, pit-out flag and the mini-sector code arrays the source publishes. Segment arrays are not published during races. Pass session_key plus driver_number to keep the response bounded.

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

Input Schema

Name	Required	Description
`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: meeting_key, session_key, driver_number, lap_number, date_start, duration_sector_1, duration_sector_2, duration_sector_3, i1_speed, i2_speed, is_pit_out_lap, lap_duration, st_speed.
`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)
`lap_number`	No	Lap number within the session, starting at 1 example(8)
`meeting_key`	No	Positive meeting key from openf1-meetings, or `latest` for the current meeting example(1299)
`session_key`	No	Positive session key from openf1-sessions, or `latest` for the current session example(11408)
`driver_number`	No	Positive permanent driver number (see openf1-drivers) example(1)
`is_pit_out_lap`	No	Only pit-out laps
`lap_duration_gte`	No	Inclusive minimum lap duration, in seconds
`lap_duration_lte`	No	Inclusive maximum lap duration, in seconds

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it lists returned fields, notes that segment arrays are not published during races, and advises on scoping to keep responses bounded. It does not discuss permissions, rate limits, or pagination, but for a read-style data tool this is a solid disclosure.

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?

Two dense sentences that front-load the resource, then move through return fields, an availability caveat, and a scoping tip. Every sentence earns its place with no filler.

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 10-parameter, all-optional tool with no output schema or annotations, the description supplies the key return shape, a behavioral caveat, and scoping advice. It is nearly complete; only explicit comparison to sibling tools and any auth/rate-limit context are missing.

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 100%, so the baseline is 3. The description adds a useful scoping instruction—combine session_key and driver_number to keep the response bounded—that is not present in the schema and is valuable given 10 optional parameters.

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 specific resource (Formula 1 lap times and sectors) and enumerates the per-lap fields returned, so an agent can identify the tool immediately. It does not explicitly contrast with sibling tools like openf1_stints or openf1_session_result, leaving some differentiation to inference.

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 only usage advice is to pass session_key plus driver_number to bound the response. There is no explicit when-to-use or when-not-to-use guidance relative to sibling tools, though the per-lap scope implies its purpose.

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

Deploy Server