Skip to main content
Glama

formula1_season_results

Read-only

Get one Formula 1 season's completed race results and return one row per round with finishing position, driver, team, laps and time. Use season in four-digit form (1950 through the current season); a season with no completed rounds returns a valid empty list. Use formula1_session_results for the detailed per-session tables of one meeting.

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_season_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional four-digit championship year; the results archive serves 1950 through the current 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

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the row-per-round return shape, the included fields, and that a season with no completed rounds returns a valid empty list rather than erroring. It stops short of describing pagination or response size, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with what the tool returns before moving to input constraints and the alternative tool. Every sentence carries distinct information with no redundant framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the description need not explain return values in full, yet it still summarizes the row structure usefully. For a single-parameter, read-only query tool with full schema coverage and annotations, nothing an agent needs in order to call it correctly is 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 single season parameter is already fully documented, including its four-digit form, 1950-to-current range, and current-season default. The description largely restates those constraints and adds no syntax or format detail beyond the schema; baseline 3 is appropriate.

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?

The description opens with a specific verb and resource ('Get one Formula 1 season's completed race results') and immediately states the output grain ('one row per round with finishing position, driver, team, laps and time'). It also names the sibling it is not (formula1_session_results), so an agent can distinguish it without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: use this tool for season-level race results, and use formula1_session_results for detailed per-session tables of one meeting. It also defines the season input constraint (four-digit, 1950 onward) and the empty-result edge case, leaving little to inference.

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.