Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

openf1_championship_teams

Retrieves Formula 1 team championship standings with each team’s position and points before, during, and after a race session; non-race sessions return no standings.

Instructions

OpenF1 Formula 1 team championship standings. Returns each team'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_teams"
  }
}

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, team_name, position_start, position_current, points_start, points_current.
team_nameNoTeam name exactly as the source reports it example(McLaren)
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)

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 provided, the description carries the full burden and does disclose meaningful behavior: the empty-list edge case for non-race sessions and the fact that values reflect pre-race versus during/after-race states. It leaves out ordering of results, live-update semantics, and pagination, which keeps it 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, then return shape, then the session-type constraint. No filler and nothing redundant with the title or schema.

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?

Four optional parameters are fully documented in the schema and no output schema exists, so the description's return-value summary and session-type caveat cover the main gaps. A note on result ordering or how often standings refresh would make it fully complete for a live-standings endpoint.

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%, and the filter syntax plus every filterable attribute is already documented in the schema. The description adds no additional parameter meaning, so the baseline 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 verb+resource ('OpenF1 Formula 1 team championship standings') and states what is returned ('each team's championship position and points'). The 'team' qualifier implicitly separates it from the sibling openf1_championship_drivers, but that sibling is never named, so differentiation relies on the caller noticing the noun.

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 clear when-to-use and when-not condition: valid for race sessions only, and other session types return an empty list. It does not explicitly route the caller to openf1_championship_drivers for driver standings, so the alternative is implied rather than stated.

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