Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

formula1_team_season_results

Fetch a Formula 1 team's per-round points for a given season, including Grand Prix name, weekend date, and points scored in each round.

Instructions

One Formula 1 team's race-by-race points for a season. Returns one team's per-round points for a season: round, Grand Prix name, weekend date and the points the team scored in that round. The page lists the rounds the team appears in. The team value comes from formula1-team-standings and the upstream page matches it case-insensitively, so Mercedes and mercedes both serve the same team.

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": {
      "team": "<team>"
    },
    "name": "formula1_team_season_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYesResults-archive team value from formula1-team-standings, such as Mercedes or Williams-Renault; matched case-insensitively example(Mercedes)
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.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 disclose the return shape (round, Grand Prix name, weekend date, points) and the meaningful caveat that only rounds in which the team appears are listed. It omits error behavior, empty/unmatched-team handling, and ordering, so it is good but not complete.

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

Conciseness3/5

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

The first sentence ('One Formula 1 team's race-by-race points for a season') is near-duplicated by the second ('Returns one team's per-round points for a season'), wasting the front-loaded position on a restatement. The remaining sentences discussing coverage and case-insensitive matching do earn their place.

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?

Because there is no output schema, the description responsibly enumerates the returned fields and the round-coverage behavior, and it explains how to source the required team value. That is enough for an agent to call this correctly, with only edge-case and ordering details 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 coverage is 100%, so both parameters are already documented with types, ranges and examples. The description's notes on team-value provenance and case-insensitivity largely restate the schema text rather than adding new meaning, which matches the baseline 3.

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?

The description gives a specific verb and resource ('Returns one team's per-round points for a season') plus explicit granularity (one row per round). The word 'team' scopes it away from driver-level siblings, but it never explicitly contrasts with formula1_driver_season_results or formula1_season_results, so differentiation relies on the reader's inference.

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?

It tells the agent where the required 'team' value must come from (formula1-team-standings) and clarifies case-insensitive matching, which is real selection guidance. It stops short of stating when to prefer this over the driver- or season-level siblings, and gives no exclusion conditions.

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