Crawlora MCP

openf1_championship_teams

Read-only

Fetch team championship standings after a session, returning team_name, position_start, position_current, points_start and points_current. 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_teams"
  }
}

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.
`team_name`	No	Optional team name exactly as the drivers list reports it.
`meeting_key`	No	Optional positive meeting key, or latest.
`session_key`	No	Optional positive session key, or latest. Standings exist only for race sessions.

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, it discloses meaningful behavior: standings only exist after races, qualifying yields zero counts, live sessions fail with 503, and unknown filter attributes are rejected before the upstream call. Return shape is described in prose but that is largely duplicated by the output schema, so it stops just short of a 5.

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?

It is front-loaded with purpose and return fields, then prerequisites, then refinement — a sensible order. It is somewhat dense and the final sentence restates filter rules already present in the schema, a minor redundancy.

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, zero-required-parameter tool with a full output schema, the description covers purpose, prerequisites, failure modes, and filtering strategy. Nothing an agent needs in order to call it correctly is missing.

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 earns extra credit by naming which attributes are filterable (position_current, points_current) and giving a concrete example (filter=position_current<=3) that the schema does not. The OR/inclusive-range semantics it restates are already in the schema, so it adds value without being fully novel.

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?

The description opens with a specific verb and resource ('Fetch team championship standings after a session') and enumerates the returned fields (team_name, position_start, position_current, points_start, points_current). The 'team' qualifier makes the distinction from openf1_championship_drivers self-evident without needing to open either schema.

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?

It states exactly which session_key to supply and where to get it (a Race session_key from openf1_sessions), warns that qualifying returns count 0, and notes that a live-session call returns 503. It also explains how to narrow results with filters, which is concrete when-to-use guidance rather than inference.

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?