Skip to main content
Glama

Milésima

Search Milésima

search
Read-onlyIdempotent

Searches Milésima's Formula 1 data since 1950 for drivers, teams, circuits, seasons and Grands Prix by name, without accents or capitals, and returns each match with a line of context and its page. Use it when you are not sure of a 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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Use the language of the person asking.en
typeNoOnly one kind: driver, team, circuit, season or grand_prix.
queryYesWhat to look for: “hamilton”, “interlagos”, “1976”, “monaco 1988”.

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
langYes
queryYes
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context: the 1950-onward data window, the accented/capital-free input convention, the per-match return format, and language-specific responses.

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 dense sentences with the scope front-loaded and no filler. The routing clause sits mid-sentence rather than at the end, a minor structural nit, but every sentence carries information.

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 three-parameter search with an output schema, the description covers domain scope, input normalization, result shape and language behavior. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuinely non-schema constraint that queries must be written without accents or capitals and repeats the lang values. The type filter's meaning (one kind only) is left to the schema.

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 verb (searches) and resource (Milésima's Formula 1 data since 1950) across five named entity kinds, and says outright that matches come back with a one-line context and page link. It is clearly the fuzzy-lookup tool rather than one of the direct get_* siblings.

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?

"Use it when you are not sure of a name" is an explicit usage condition that implicitly routes exact lookups to get_driver/get_team. It gives clear context but stops short of naming an alternative or stating when not to use it.

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