Skip to main content
Glama

formula1_season_awards

Read-only

Get one Formula 1 season's award table and return the ranked entries for the requested award. award is required and is one of fastest-laps, pole-positions, fastest-pit-stops or driver-of-the-day; season is four-digit and defaults to the current championship year. The award tables cover 1950 onwards where the award exists, and an unavailable award for a season is an upstream error rather than an empty guess.

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": {
      "award": "<award>"
    },
    "name": "formula1_season_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
awardYesRequired award: fastest-laps, pole-positions, fastest-pit-stops or driver-of-the-day.
seasonNoOptional four-digit championship year. 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.6/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, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: an unavailable award for a season surfaces as an upstream error rather than an empty result, which shapes how an agent should read failures. It says nothing further about response size, ranking ties, or coverage limits.

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, front-loaded with the purpose, then constraints, then the historical/error caveat. Every sentence carries information, though the award enumeration duplicates the schema slightly.

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 two-parameter read-only lookup with an output schema, this is essentially complete: required input, valid values, default behavior, historical coverage, and error semantics are all stated. Only sibling disambiguation and any ranking-ordering detail are missing.

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%, so the schema already documents both parameters, and the description largely restates the accepted award values and the season default. It adds only the semantic nuance that season is a four-digit championship year and that awards are only defined from 1950 onward. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get one Formula 1 season's award table') plus the scope of what is returned ('ranked entries for the requested award'). It is clear what the tool does, but it never distinguishes itself from the similar award-related siblings (formula1_json_awards, formula1_json_season_award), so an agent cannot rule them out from this text alone.

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 context for use: award is required with the four valid values, season defaults to the current championship year, and the data starts at 1950 where the award exists. It stops short of naming alternatives or stating when not to use it, but the practical conditions for calling it are all present.

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.