Skip to main content
Glama

Milésima

Formula 1 circuit and Grand Prix history

get_grand_prix_history
Read-onlyIdempotent

The history of a circuit since 1950: who won every Grand Prix held there (most recent first, with grid position, race time and fastest lap), who has won the most, the race lap record, length, corners and the next Grand Prix there. Accepts the circuit, its city or the Grand Prix name. 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": {
      "circuit": "<circuit>"
    },
    "name": "get_grand_prix_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Use the language of the person asking.en
limitNoHow many winners, most recent first, 1-80. Default 20.
circuitYesThe circuit (“Monza”, “Silverstone”), its city (“Monte Carlo”) or a Grand Prix name (“British Grand Prix”).

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
langYes
circuitYes
cornersNo
winnersYes
last_yearNo
length_kmNo
most_winsNo
first_yearNo
lap_recordNo
grands_prixNo
total_winnersYes
next_grand_prixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds real behavioral detail beyond that: results are ordered most recent first, coverage starts in 1950, the response language follows the lang parameter, and the payload includes derived aggregates ('who has won the most') and forward-looking data ('the next Grand Prix there'). Error behavior for an unrecognized circuit name is the main omission.

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 a single dense sentence that front-loads the resource and then enumerates the returned fields without filler. The nested parentheticals make it slightly harder to scan, but no sentence is wasted.

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 shapes, and annotations carry the safety profile; the description still explains scope (since 1950), ordering and language handling. What remains missing is only edge-case behavior, such as what happens for an ambiguous or unknown circuit name.

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%, so all three parameters are already documented in the schema, including the circuit/city/GP-name flexibility for 'circuit'. The description restates that same flexibility and the language behavior rather than adding new semantics such as format hints or fallback rules. 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 states a specific resource and the exact payload: 'who won every Grand Prix held there (most recent first, with grid position, race time and fastest lap)... the race lap record, length, corners'. That is far beyond restating the title and lets an agent know this is a circuit-level historical record rather than calendar, driver or results data. It does not name a sibling to route against, so it stops at 4.

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?

'Accepts the circuit, its city or the Grand Prix name' tells the agent what inputs are valid, which implicitly signals this is the tool for circuit/GP history. However, there is no explicit when-to-use versus get_calendar, get_session_results or search, and no exclusion for cases where the circuit is unknown.

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