Skip to main content
Glama

Milésima

Formula 1 team profile

get_team
Read-onlyIdempotent

The profile of any Formula 1 team or constructor since 1950: seasons, Grands Prix, wins, starts from first place on the grid, podiums, constructors' and drivers' titles, current drivers and the teams it comes from. 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": {
      "team": "<team>"
    },
    "name": "get_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Use the language of the person asking.en
teamYesThe team's name (“Ferrari”, “McLaren”, “Red Bull”) or Milésima slug (“red-bull”).

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
langYes
nameYes
winsYes
notesYes
yearsYes
statusYes
countryNo
lineageNo
podiumsYes
seasonsYes
grands_prixYes
also_matchedNo
source_namesNo
drivers_titlesYes
current_driversNo
constructors_titlesYes
starts_from_first_place_on_gridYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so safety is covered. The description adds useful scope context (all history back to 1950) but says nothing about behavior for unknown or ambiguous team names, whether the profile includes current-season in-progress data, or how the language affects field naming.

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 well-formed sentence with the core resource front-loaded and the returned-field list and language note trailing behind it. The enumeration is dense but each item aids tool selection; nothing reads as 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?

An output schema exists, so return formatting need not be explained, and the annotations cover the safety profile. The definition is complete for a simple two-parameter read tool; only edge-case behavior (unknown team, ambiguous names, partial-season data) is left unaddressed.

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%: both 'team' (name or Milésima slug) and 'lang' (es/en/it, default en) are fully documented in the schema. The description only restates the language behavior already present, adding no syntax, normalization, or fallback meaning beyond the structured fields.

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 names a concrete resource ('the profile of any Formula 1 team or constructor since 1950') and enumerates the fields it returns (seasons, wins, poles, podiums, titles, current drivers), which makes it easy to separate from get_driver, get_calendar, or get_standings. It lacks explicit sibling differentiation, but the resource boundary is unambiguous.

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 is only implied: the temporal scope ('since 1950') and the phrase 'any Formula 1 team or constructor' signal when the tool applies, but there is no when-to-use versus when-not guidance and no routing to get_driver for driver-level data. The only explicit instruction concerns language selection, which is a parameter choice rather than tool choice.

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