Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

openf1_championship_drivers

Fetch Formula 1 driver championship standings with positions and points before, during, or after a race session, filtered by meeting, session, or driver.

Instructions

OpenF1 Formula 1 driver championship standings. Returns each driver's championship position and points before the race and during/after it. Available for race sessions only; other session types return an empty list.

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

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, driver_number, position_start, position_current, points_start, points_current.
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)
driver_numberNoPositive permanent driver number (see openf1-drivers) example(1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does disclose a non-obvious trait: non-race session types yield an empty list rather than an error. It also characterizes the returned data as before-race versus during/after-race snapshots. Remaining gaps are pagination and auth requirements, which are minor for a read route.

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 sentences, zero filler. The purpose and return content come first, with the session-type restriction as a compact follow-on.

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?

Given four optional parameters, full schema coverage, no annotations and no output schema, the description supplies purpose, return content, and a key session-type caveat. Supporting details like pagination limits or typical result size are absent but not essential for correct invocation.

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%, with each of the four parameters fully documented upstream, including the filter grammar and 'latest' shorthand. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 (OpenF1 Formula 1 driver championship standings) and states exactly what is returned: each driver's championship position and points, both before and during/after the race. The word 'driver' implicitly separates it from openf1_championship_teams, but no sibling is named explicitly, which keeps it just 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?

It gives a concrete applicability boundary: 'Available for race sessions only; other session types return an empty list.' That is a real when-not condition an agent can act on. It does not point to an alternative tool for non-race sessions, but the exclusion itself is clear.

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