Skip to main content
Glama

Crawlora MCP

formula1_driver_season_results

Read-only

Get one Formula 1 driver's race-by-race results for a season and return round, Grand Prix, date, constructor, finishing position or DNF/NC/DSQ text, and points. driver_code is the real key from formula1_driver_standings and is required; season covers 1950 through the current season and defaults to the current one, while driver_slug is decorative and only builds the URL. The page lists the rounds the driver appears in, not every championship round, and an unknown code is a 404.

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": {
      "driver_code": "<driver_code>"
    },
    "name": "formula1_driver_season_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional four-digit championship year, 1950 through the current season. Defaults to the current season.
driver_codeYesRequired uppercase driver code from formula1-driver-standings, such as ANDANT01. The code is the page's real key; the slug is decorative.
driver_slugNoOptional driver profile slug used only in the upstream URL; a placeholder is used when omitted. The driver code selects the data.

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.3/5.0
Behavior5/5

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

Annotations already cover readOnly and openWorld, and the description adds behavior those do not: the result lists only rounds the driver appears in rather than every championship round, and an invalid code produces a 404. It also flags that the slug is non-functional, preventing a plausible misuse.

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 dense sentences with the core action and return fields front-loaded. There is minor repetition ('real key' / 'decorative slug' appear in both description and schema), but no sentence is filler.

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 three-parameter read tool with an output schema, the description covers scope of returned rows, key sourcing, defaults, and error behavior. A note on how it differs in intent from season-wide or team result tools would make it fully self-sufficient.

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%, so all three parameters are already documented; the description largely restates that driver_code is the real key, season spans 1950–current with a default, and driver_slug is decorative. Useful reinforcement but little meaning beyond the schema.

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?

States a specific verb and resource ('Get one Formula 1 driver's race-by-race results for a season') and enumerates the returned fields (round, Grand Prix, date, constructor, finishing position/DNF/NC/DSQ, points). The phrase 'one driver's' plus the field list separates it from season-wide or standings siblings without needing to inspect the schema.

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 concrete conditions: driver_code is required and must come from formula1_driver_standings, season defaults to the current one, and an unknown code yields a 404. It does not explicitly name when a different sibling (e.g. season-wide or team results) is the better choice, which keeps it just short of 5.

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