Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

openf1_stints

Fetch Formula 1 stint and tyre compound records by session, driver, lap range, or compound to analyze race strategy, stint timing, and tyre age.

Instructions

OpenF1 Formula 1 stints and tyre compounds. Returns each continuous driving period on one set of tyres: stint number, starting and ending lap, tyre compound and tyre age at the start. Use session_key with driver_number for one driver's strategy.

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

Input Schema

NameRequiredDescriptionDefault
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, session_key, stint_number, driver_number, lap_start, lap_end, compound, tyre_age_at_start.
compoundNoTyre compound; one of SOFT, MEDIUM, HARD, INTERMEDIATE, WET Enums(SOFT,MEDIUM,HARD,INTERMEDIATE,WET) example(SOFT)
lap_end_gteNoInclusive minimum stint ending lap
lap_end_lteNoInclusive maximum stint ending lap
meeting_keyNoPositive meeting key from openf1-meetings, or `latest` for the current meeting example(1299)
session_keyNoPositive session key from openf1-sessions, or `latest` for the current session example(11408)
stint_numberNoStint number within the session, starting at 1
driver_numberNoPositive permanent driver number (see openf1-drivers) example(1)
lap_start_gteNoInclusive minimum stint starting lap
lap_start_lteNoInclusive maximum stint starting lap
tyre_age_at_start_gteNoInclusive minimum tyre age at stint start, in laps example(3)
tyre_age_at_start_lteNoInclusive maximum tyre age at stint start, in laps

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 exist, so the description carries the full burden. It does disclose the shape of the result (per-stint records with starting/ending laps and compound), which signals this is a read-only listing. However, it says nothing about ordering, result size, pagination, rate limits, or what an empty result means — meaningful gaps for a tool with no annotation coverage.

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?

Two front-loaded sentences: the first states the resource and the returned fields, the second gives the primary usage pattern. The opening 'OpenF1 Formula 1 stints and tyre compounds' is slightly label-like and repeats the tool name, but overall there is little wasted text.

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?

With 12 optional parameters, no output schema and no annotations, the description does reasonably well by explaining what a stint record contains, which substitutes for the missing output schema. It is a bit light on how the paginated or bounded result behaves, but an agent has enough to call it correctly.

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 documents every filter, enum and range bound in detail. The description adds only the session_key + driver_number combination hint for per-driver strategy queries; it does not explain how the repeatable `filter` attribute syntax interacts with the typed shortcut 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 concrete verb and resource (returns Formula 1 stints) and enumerates the fields returned: stint number, starting/ending lap, tyre compound, tyre age at start. It is clearly distinguishable from lap or pit tools by the 'continuous driving period on one set of tyres' framing, though it never names a sibling to contrast with.

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?

One usage hint is given: 'Use session_key with driver_number for one driver's strategy.' That tells the agent how to scope to a single driver but gives no when-not guidance, no mention of combining with meeting_key or compound, and no alternative tools for other views of race strategy.

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