Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

formula1_driver_season_results

Retrieve a Formula 1 driver's race-by-race season results, including round, Grand Prix, date, constructor, finishing position or DNF/NC/DSQ, and points.

Instructions

One Formula 1 driver's race-by-race results for a season. Returns one driver's per-round results for a season: round, Grand Prix name, weekend date, the constructor the driver raced for in that round, finishing position or a non-numeric classification such as DNF, NC or DSQ, and the points scored. The page lists the rounds the driver appears in, not every round of the championship. The driver code is the page's real key; the slug only builds the URL and a wrong slug still serves the driver.

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
seasonNoFour-digit championship year, 1950 through the current season; defaults to the current season example(2026)
driver_codeYesUppercase driver code from formula1-driver-standings, such as ANDANT01 example(ANDANT01)
driver_slugNoDriver profile slug used only in the upstream URL; a placeholder is used when omitted example(kimi-antonelli)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it enumerates the returned fields, warns about non-numeric classifications like DNF/NC/DSQ, and discloses that the page lists only rounds the driver appears in rather than the full calendar. It omits failure behavior for invalid driver codes and any rate-limit or pagination notes, 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.

Conciseness4/5

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

The return-field list is dense and useful, and the key/slug caveat is placed last where it matters. The opening two sentences are partially redundant, restating 'one driver's ... results for a season' before elaborating, which costs a little efficiency.

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 read-only scrape tool with no annotations and no output schema, the description covers return shape, edge-case values, coverage caveats, and parameter key behavior. Remaining gaps, such as error handling for an unknown driver code, are minor but real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema by clarifying that driver_code is the real key and that the slug only builds the URL, so even a wrong slug still resolves the driver. The season parameter's semantics are left entirely to the schema.

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: one F1 driver's race-by-race results for a season. The driver-scoped framing implicitly separates it from season-wide and team-scoped siblings, though no sibling is named explicitly.

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 context is implied (per-driver, per-season lookup) and the description adds an operational caveat that not every championship round may appear. It never states when to pick this over formula1_season_results or formula1_team_season_results, leaving the agent to infer the choice from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools