Crawlora MCP

openf1_race_control

Read-only

List race-control messages for a session, returning category, flag, scope, lap_number, qualifying_phase and message text. Use session_key with category or flag to filter incidents, flags and safety cars; a valid empty match returns count 0 and a live-session call returns 503. For finer queries, add repeatable filter= (operators >=, <=, =, >, <) to narrow by category or flag, e.g. filter=category=SafetyCar; repeated filters on one attribute are OR'ed and ranges are inclusive.

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

Input Schema

Name	Required	Description
`flag`	No	Optional flag type, for example YELLOW or DOUBLE YELLOW.
`scope`	No	Optional event scope. Values: Track, Driver, Sector.
`filter`	No	Repeatable upstream filter expression written as <attribute><operator><value> with operators >=, <=, =, > and <. Repeated filters on the same attribute are OR'ed, ranges are inclusive, and unknown attributes or values are rejected before the upstream call.
`sector`	No	Optional track sector the message refers to, starting at 1.
`date_to`	No	Optional message upper bound; RFC3339 or YYYY-MM-DD.
`category`	No	Optional message category, for example Flag or SafetyCar. Values observed: CarEvent, Drs, Flag, Other, SafetyCar, SessionStatus.
`date_from`	No	Optional message lower bound; RFC3339 or YYYY-MM-DD.
`lap_number`	No	Optional race lap number the message refers to.
`meeting_key`	No	Optional positive meeting key, or latest.
`session_key`	No	Optional positive session key, or latest.
`driver_number`	No	Optional positive driver number the message is about.
`qualifying_phase`	No	Optional qualifying phase, 1 to 3.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses that a valid empty match returns count 0, that a live-session call returns 503, and that repeated filters on one attribute are OR'ed with inclusive ranges. That is real operational behavior an agent could not infer from annotations alone; it misses things like pagination or default session resolution.

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 its return fields, then filtering guidance, then the advanced filter syntax. Dense but no filler; the only slight redundancy is restating the OR/inclusive-range rules that the schema also carries.

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, zero-required read tool with an output schema and annotations, the description covers the filtering workflow, empty-result behavior and the 503 failure mode. Remaining gaps (how "latest" is resolved, result limits) are modest given the output schema carries return shape.

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 every parameter is already documented, and the filter syntax, OR semantics and inclusive ranges appear in both places. The description's only added value is a worked example (filter=category=SafetyCar) and the hint that session_key pairs with category/flag, which is marginal over 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?

States a specific verb and resource ("List race-control messages for a session") and enumerates the returned fields (category, flag, scope, lap_number, qualifying_phase, message text), so the agent knows exactly what it gets. It does not name or contrast any sibling tool, but the resource is clearly disjoint from the other openf1 datasets.

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 concrete usage context: combine session_key with category or flag to isolate incidents, flags and safety cars, and add filter expressions for finer narrowing. It lacks explicit when-not-to-use guidance or a named alternative, so it stops short of a 5.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?