Skip to main content
Glama

Crawlora MCP

formula1_team_season_results

Read-only

Get one Formula 1 team's race-by-race points for a season and return round, Grand Prix, date and points. team is the results-archive value from formula1_team_standings and is required; the page matches it case-insensitively, so Mercedes and mercedes serve the same team. season covers 1950 through the current season and defaults to the current one. The page lists the rounds the team appears in, and an unknown team 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": {
      "team": "<team>"
    },
    "name": "formula1_team_season_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYesRequired results-archive team value from formula1-team-standings, such as Mercedes or Williams-Renault. The page matches it case-insensitively.
seasonNoOptional four-digit championship year, 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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior: case-insensitive team matching ('Mercedes and mercedes serve the same team'), the 1950-to-current season bound with a current-season default, and a 404 for unknown teams. Pagination or page-size behavior is not disclosed despite the page-oriented phrasing.

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?

Front-loaded with purpose and return shape, then parameter facts, then the failure mode. Four compact sentences with no filler, though the case-insensitivity and season-range statements echo the schema descriptions and could be trimmed.

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?

An output schema exists and the description still summarizes the returned columns; annotations cover safety; both parameters are explained. Complete for a two-parameter read tool, with only pagination/result-limit behavior left unstated.

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 in the schema, and the description largely restates the same facts (case-insensitive matching, 1950-to-current range, current-season default). The one addition — that `team` is the results-archive value from formula1_team_standings — duplicates the schema text verbatim, so 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?

States a specific verb and resource ('Get one Formula 1 team's race-by-race points for a season') and enumerates the returned fields (round, Grand Prix, date, points). The 'one team' scoping distinguishes it from driver-level and whole-season siblings without needing to name them.

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 ('the results-archive value from formula1_team_standings'), which is real routing guidance to a sibling. It does not explicitly say when to prefer formula1_driver_season_results or formula1_season_results instead, so there is no stated exclusion set.

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