Skip to main content
Glama

Milésima

Formula 1 season calendar

get_calendar
Read-onlyIdempotent

Every round of a Formula 1 season (1950 onwards): Grand Prix, circuit and city, weekend dates, race start time in UTC, sprint weekends, cancelled rounds and the winner of each race already run. Responds in the requested language (lang: es, en, it).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_calendar"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
doneYes
langYes
yearYes
roundsYes
sprintsYes
calendarYes
cancelledNo

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: historical coverage back to 1950, inclusion of cancelled rounds, sprint-weekend flagging, UTC-normalised start times, and that winners are returned for rounds already run.

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?

One tightly written sentence with the resource and its full payload front-loaded, followed by the language note. Every clause carries information, though the dense comma-list is mildly harder to scan than short separated sentences would be.

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, return values need not be explained, and both optional parameters are covered. The description is suitably complete for a two-parameter, read-only lookup; it simply omits any routing guidance against the sibling result/history tools.

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% and both parameters are fully described in the schema, including the enum values and the 1950+ / omit-for-current-season behaviour. The description only restates the language behaviour ('lang: es, en, it') and the 1950 onwards span, adding little beyond the structured fields, so the baseline of 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 names a specific resource (a Formula 1 season calendar) and enumerates exactly what each round contains: Grand Prix, circuit, city, weekend dates, UTC start time, sprint weekends, cancelled rounds and past winners. That enumeration makes it distinguishable in practice from get_session_results and get_grand_prix_history, but no sibling is named and no explicit boundary is drawn with the race-results tool that also returns winners.

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 scope ('every round of a season') suggests using it for season-level overviews, and the schema note about omitting year covers the current season. There is no statement of when to prefer this over get_next_session, get_grand_prix_history or get_session_results, and no exclusions or prerequisites.

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