Skip to main content
Glama

formula1_race_calendar

Read-only

Get one Formula 1 season's published calendar and return each round's event_slug, official and short names, country, date text, start/end dates, test-event flag, completion flag and status. Use the event_slug with formula1_race_hub; the calendar covers 2018 onwards and a season without a published calendar is an upstream error, not an empty table. Season defaults to the current championship year.

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": "formula1_race_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional four-digit championship year; the calendar pages cover 2018 through next season. Defaults to the current season.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely useful error semantics (a season without a published calendar surfaces as an upstream error, not an empty result) plus the 2018-onwards coverage window. It does not discuss pagination, response shape, or rate/latency behavior, so it adds moderate rather than rich context beyond the annotations.

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?

Three sentences, front-loaded with the action and scope, then the routing hint, then the caveat. The enumeration of returned fields is slightly redundant given a dedicated output schema, but it stays compact and readable.

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?

For a single optional-parameter, read-only lookup with an output schema, the description covers scope, default behavior, downstream usage, and error semantics. Nothing essential to invoking it correctly is missing, though the return-field listing duplicates what the output schema already provides.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains the four-digit year and the 2018-through-next-season range. The description only restates the default (current championship year), which is already present in the schema, adding no new meaning.

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?

Opens with a specific verb and resource ("Get one Formula 1 season's published calendar") and scopes it to a single season, listing the round-level fields returned. It also points to formula1_race_hub as the downstream consumer, which differentiates it from the sibling set without ambiguity.

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?

Gives clear operational context: the calendar covers 2018 onwards, season defaults to the current championship year, and a missing published calendar is an upstream error rather than an empty table. It stops short of stating when to prefer a different calendar-like sibling, but the event_slug handoff to formula1_race_hub makes the intended workflow explicit.

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.