Skip to main content
Glama

Milésima

Formula 1 championship standings

get_standings
Read-onlyIdempotent

The drivers' or constructors' championship of a season (1950 onwards; constructors from 1958): position, points, gap to the leader, wins and podiums, how the title stands and, for constructors, the points of each driver. Optionally as it stood after a given round. Responds in the requested language (lang: es, en, it).

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": "get_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Use the language of the person asking.en
yearNoSeason year (1950 onwards). Omit for the current season.
limitNoHow many positions, 1-60. Default 30.
after_roundNoThe standings after this round. Omit for the latest.
championshipNodrivers or constructors. Default drivers.drivers

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
langYes
yearYes
titleNoHow the title stands, as the website says it
standingsYes
after_roundYes
provisionalNo
championshipYes
total_roundsYes
after_grand_prixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuine domain behavior: constructors' championships exist only from 1958 and the language of the response follows the lang parameter — useful facts not present in the annotations.

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?

A single dense sentence that front-loads the subject and packs the returned fields and scope bounds into parentheses. It borders on run-on and the trailing 'lang: es, en, it' note repeats schema content, but there is no filler.

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?

With an output schema present the description need not explain return values, and it still summarizes them; with 100% schema coverage the parameters are handled. The domain constraints (year floors, snapshot semantics) are supplied, leaving only minor gaps such as default-sort and limit behavior.

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 coverage is 100% and all five parameters carry descriptions, so the schema already does the heavy lifting. The description only restates two of them (championship type selection and the after-round snapshot) and adds no format or edge-case detail beyond that; baseline 3 applies.

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 resource (drivers' or constructors' championship standings for a season) and enumerates the returned content: position, points, gap to leader, wins, podiums, plus per-driver points for constructors. The distinction between drivers and constructors, and the 1950/1958 domain bounds, make it unmistakable against siblings like get_session_results or get_grand_prix_history.

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

Usage Guidelines3/5

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

Usage conditions are implied through scope notes ('1950 onwards; constructors from 1958', 'Optionally as it stood after a given round') but there is no explicit when-to-use versus when-to-prefer-an-alternative guidance, and no sibling is named. An agent can infer the right context but must reason about it rather than being told.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources