Crawlora MCP

openf1_championship_drivers

Read-only

Fetch driver championship standings after a session, returning position_start, position_current, points_start and points_current for each driver. Use a Race session_key from openf1_sessions because standings appear after races (qualifying returns count 0); a live-session call returns 503. For finer queries, add repeatable filter= (operators >=, <=, =, >, <) to narrow by position_current or points_current, e.g. filter=position_current<=3; 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_championship_drivers"
  }
}

Input Schema

Name	Required	Description
`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.
`meeting_key`	No	Optional positive meeting key, or latest.
`session_key`	No	Optional positive session key, or latest. Standings exist only for race sessions.
`driver_number`	No	Optional positive driver number.

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

A4.6/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses failure behavior (503 on live sessions, zero counts for qualifying) and filter evaluation semantics (OR across repeated filters, inclusive ranges). It does not cover pagination or result size, but the output schema already documents the return shape.

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: what it returns, then the constraint on session_key, then filter usage. Slightly dense, and the filter OR/inclusive rules repeat what the schema's filter description already says, but nothing is padded or off-topic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with an output schema, full schema coverage and annotations, the description supplies everything an agent needs: correct session type, failure conditions, and filter syntax, with no material gaps.

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 still adds value with a concrete filter example (filter=position_current<=3) and a note that unknown attributes or values are rejected before the upstream call, which is semantic rather than a restatement of the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (fetch) plus resource (driver championship standings) and even enumerates the returned fields (position_start, position_current, points_start, points_current). The word 'driver' separates it cleanly from the sibling openf1_championship_teams, and no schema needs to be opened to understand what it does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance: use a Race session_key from openf1_sessions, with the reason stated (standings appear after races, qualifying returns count 0), plus a when-not condition (live-session calls return 503) and a named sibling as the source of the key.

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?