Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_season_awards

Retrieve Formula 1 per-round season award winners for fastest laps, pole positions, fastest pit stops, or driver of the day, with round, meeting id, Grand Prix name, winner, and time.

Instructions

Formula 1 season award winners by round. Returns one season award's per-round winner list: the DHL Fastest Lap, Pirelli Pole Position, DHL Fastest Pit Stop (a team award) or Salesforce Driver of the Day. Each row carries the round, numeric meeting id, Grand Prix name, winner and the award time where the page renders one. An award the site does not publish for the requested season returns HTTP 400 with an explicit message.

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
awardYesSeason award: fastest-laps, pole-positions, fastest-pit-stops or driver-of-the-day
seasonNoFour-digit championship year, 1950 through the current season; defaults to the current season example(2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does well to disclose the row fields (round, meeting id, GP name, winner, optional award time) and the explicit HTTP 400 behavior for unpublished awards, but says nothing about whether results are bounded to a full season, ordering, or empty-vs-error conditions beyond the 400 case.

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 front-loaded sentences with the return shape immediately after the purpose statement, and no filler wording. It is dense but every clause carries information an agent can act on.

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, no-output-schema tool, the description gives a usable picture of the return rows and the failure mode, which is what an agent needs to interpret results. The gap is the lack of any season-scoping or result-size guidance, but that is a modest omission.

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% and the enum already constrains the award values, so the baseline is 3. The description adds real meaning by mapping the slug values to their full award names and noting the pit-stop award is team-based, but it adds nothing about the season parameter (range, default, or format).

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?

Names a specific verb+resource ('season award winners by round') and enumerates exactly which award datasets are returned, including that fastest-pit-stops is a team award. It does not explicitly distinguish itself from the similarly named siblings like formula1_json_awards or formula1_json_season_award, leaving some ambiguity for an agent choosing between them.

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?

Implicitly communicates usage by stating it returns one award at a time, which tells the agent it must pick a single award per call, and it flags the failure mode for unpublished awards. However, it never says when to prefer this tool over the award-related siblings or what prerequisites exist.

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