Skip to main content
Glama

Milésima

Formula 1 session results

get_session_results
Read-onlyIdempotent

The classification of a Formula 1 session of any season since 1950: race and sprint (position, driver, team, laps, total time or gap to the winner to the thousandth, points, grid position, status), qualifying (Q1/Q2/Q3 times and who was knocked out) or practice (best lap, gap, laps). From 2023 every session; before 2023 only the race. Marks a classification that is still provisional. Responds in the requested language (lang: es, en, it).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "grand_prix": "<grand_prix>"
    },
    "name": "get_session_results"
  }
}

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.
sessionNoWhich session. Default race.race
grand_prixYesThe Grand Prix: its name, country, city or circuit in English, Spanish or Italian (“Monaco”, “Italian Grand Prix”, “Monza”, “Las Vegas”) or its Milésima slug (“las-vegas”).

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
kindYes
langYes
liveYes
statusYesThe session status as the website writes it
circuitNo
ends_atYesISO 8601, UTC
resultsYes
sessionYespractice-1, practice-2, practice-3, sprint-qualifying, sprint, qualifying or race
starts_atYesISO 8601, UTC
grand_prixYes
title_noteNo
total_lapsNo
fastest_lapNo
provisionalNoThe classification may still change after penalties
session_nameYes
scheduled_lapsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds two valuable behavioral traits beyond that — the pre-2023 race-only coverage limit and the 'provisional' classification marker, which warns the agent the data may change. That is real added context but thin relative to what a 4-5 would require, and return shape is left to the output schema.

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?

Front-loads the resource and the returned classification before qualifying the session types and coverage rules. The parenthetical field lists are information-dense and each clause carries payload detail, though the single run-on sentence with three stacked field groups is heavier than it needs to be.

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?

Output schema exists, yet the description still conveys the essentials an agent needs: what sessions are available, the historical coverage boundary, provisional-data warning, and language handling. Nothing required for correct invocation is missing for a four-parameter read-only lookup.

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?

With 100% schema description coverage the baseline is 3, and the description adds only that answers come back in the requested language (lang: es, en, it) — a point the schema already documents in the lang property. The grand_prix flexibility (name, country, city, circuit, slug) and the year default are fully specified in the schema and not extended here.

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?

States a specific verb and resource ('the classification of a Formula 1 session') and enumerates the exact payload — race/sprint fields, qualifying Q1/Q2/Q3, practice best lap — so the agent knows precisely what comes back. It never names a sibling (get_calendar, get_next_session) to contrast against, so differentiation is achieved only implicitly through the described content.

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?

Gives substantive applicability constraints: 'From 2023 every session; before 2023 only the race' tells the agent when the results will be complete versus race-only, which is genuine when-to-use guidance for historical queries. It stops short of explicit exclusions or routing to alternatives for schedules or upcoming sessions.

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