Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

openf1_car_data

Retrieve Formula 1 car telemetry samples by driver and date window, including speed, RPM, gear, throttle, brake, and DRS status.

Instructions

OpenF1 Formula 1 car telemetry samples. Returns car telemetry at roughly 3.7 Hz: speed, engine RPM, gear, throttle percentage, brake flag and DRS status for each sample timestamp. Always pass driver_number and a date window: a whole-session request without a driver is rejected upstream as too much data at once.

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

Input Schema

NameRequiredDescriptionDefault
drsNoExact DRS status code
brakeNoBrake flag, 0 or 1
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, driver_number, date, rpm, speed, n_gear, throttle, brake, drs.
n_gearNoExact gear, 0 to 8
date_toNoInclusive upper bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-08)
rpm_gteNoInclusive minimum engine RPM
rpm_lteNoInclusive maximum engine RPM
date_fromNoInclusive lower bound; RFC3339 timestamp or YYYY-MM-DD example(2026-11-07)
speed_gteNoInclusive minimum speed in km/h example(315)
speed_lteNoInclusive maximum speed in km/h
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)
throttle_gteNoInclusive minimum throttle percentage
throttle_lteNoInclusive maximum throttle percentage
driver_numberNoPositive permanent driver number (see openf1-drivers) example(1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/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 full burden. It usefully discloses the sampling rate and the upstream rejection behavior, but says nothing about response size, pagination, ordering by timestamp, or auth/rate-limit characteristics for a 3.7 Hz multi-hour telemetry stream — the practical risk of an unmanageably large response is only half-addressed.

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?

Three sentences, front-loaded with the resource and payload, then the constraint. No filler, no restatement of the tool name.

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 15 params all fully documented and no output schema, the description carries the right load: it names return fields and the key scoping rule. It could have added timestamp ordering or a hint about expected data volume per driver-window, which is the main remaining gap for a high-frequency telemetry route.

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 covers 100% of parameters, so the baseline is 3. The description earns an extra point by flagging that driver_number and a date range are effectively required in practice even though the schema's required array is empty, which is meaning beyond what the schema states.

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?

States a specific verb and resource ("OpenF1 Formula 1 car telemetry samples") and enumerates the exact fields returned (speed, RPM, gear, throttle, brake, DRS) plus the ~3.7 Hz sampling rate, so the agent knows precisely what comes back. It never names a sibling to differentiate from, even though openf1_location and openf1_position sit close to it, so it stops short of a 5.

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 a concrete, actionable rule: always pass driver_number plus a date window, and explains the reason (upstream rejects whole-session requests without a driver). That is real usage guidance rather than a vague hint, but no alternative tool is named for the case where the agent wants session-wide telemetry.

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