Skip to main content
Glama

Milésima

Formula 1 driver profile

get_driver
Read-onlyIdempotent

The profile of any Formula 1 driver since 1950: country, date of birth, car number, teams, first and last race, championship years and career figures (starts, wins, podiums, points, titles, fastest laps; poles only from 2023 — before that, starts from first place on the grid), plus the current season. 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": {
      "driver": "<driver>"
    },
    "name": "get_driver"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Use the language of the person asking.en
driverYesThe driver's name (“Fernando Alonso”, “Senna”, “Kimi Antonelli”) or Milésima slug (“fernando-alonso”).

Output Schema

NameRequiredDescriptionDefault
ageNo
urlYesCanonical page on milesima.profblu.com: cite it
codeNo
langYes
nameYes
notesYes
teamsYes
careerYes
statusYes
countryNo
last_raceNo
birth_dateNo
car_numberNo
first_raceNo
poles_noteNo
also_matchedNoOther drivers that matched the name
current_teamNo
current_seasonNo
championship_yearsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real contribution is domain-level behavior: the poles-only-from-2023 caveat with the historical fallback definition, the 'current season' inclusion, and response localization. That is substantive context an agent could not derive from structured fields.

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?

Two sentences, front-loaded with the resource and scope, then the data caveats. The parenthetical about poles is dense but earns its place because it prevents a real misinterpretation; nothing is filler.

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 two-parameter read tool with an output schema, the description covers everything an agent needs: coverage window, returned field families, historical data caveats, season currency, and language behavior. Return-value details are properly left to the output schema.

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%, with both the driver and lang parameters fully documented in the schema including the enum and slug example. The description only restates the lang options ('lang: es, en, it') without adding syntax or resolution rules for ambiguous driver names, so it sits at the baseline.

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 names a specific verb and resource ('profile of any Formula 1 driver') and bounds the scope precisely ('since 1950', 'plus the current season'). The enumerated fields (country, DOB, teams, championships, career figures) make it immediately distinguishable from get_team, get_standings, and get_session_results.

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?

Coverage of 'any driver since 1950' implies when the tool applies, but there is no explicit when-not guidance or pointer to a sibling such as get_team or search for adjacent lookups. An agent can infer the use case, but nothing steers it away from alternatives when a query is ambiguous.

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