Skip to main content
Glama

Milésima

Next Formula 1 session

get_next_session
Read-onlyIdempotent

What is on now or next in Formula 1: the live or next session (Grand Prix, round, circuit, start time in UTC and status), the latest result and the championship leaders (or the champions in the off-season), with the canonical Milésima page of each. 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_next_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Use the language of the person asking.en

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on milesima.profblu.com: cite it
langYes
stateYes
circuitNo
leadersNo
sessionNo
championsNo
latest_resultNo

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context beyond them: the payload is a composite snapshot, it degrades gracefully in the off-season by returning champions instead of leaders, and the answer language is derived from the lang input. It does not discuss caching or freshness of the 'live' session status.

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 front-loaded sentence that leads with the core question 'What is on now or next in Formula 1'. The nested parenthetical inventory is dense but each element is informative; no filler sentences.

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 detail return values, and annotations cover the safety profile. The description still supplies the off-season fallback and language behavior, leaving only minor gaps around data freshness and how the live/next choice is made.

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 the single enum parameter is fully documented in-schema, so the baseline is 3. The description restates the accepted languages (es, en, it) but adds no meaning beyond the schema, such as what happens with an unsupported locale or whether statuses are translated.

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 (Formula 1) and enumerates exactly what comes back: live/next session with Grand Prix, round, circuit, UTC start time and status, plus latest result, championship leaders and canonical page links. It is clear what the tool returns, but it does not explicitly distinguish itself from overlapping siblings such as get_session_results or get_standings, which appear to cover parts of the same payload.

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 implied by the framing 'What is on now or next', suggesting a quick status/overview call, but there is no explicit when-to-use, when-not-to-use, or pointer to a more targeted sibling for results or standings. The agent must infer the selection logic from the sibling names alone.

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