Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_seasons

Lists every Formula 1 championship season published by the results archive, newest first, and marks the current season so you can choose a valid season value for related F1 routes.

Instructions

Formula 1 seasons published by the results archive. Returns every championship season the formula1.com results archive publishes, newest first, with the season the site currently defaults to marked as current. This is the discovery surface for the season parameter the other Formula 1 routes accept: the archive covers 1950 through the current season.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "formula1_seasons"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does a fair job: it discloses ordering ('newest first'), the presence of a 'current' marker reflecting the site default, and the coverage window of 1950 to present. It omits any statement about pagination or payload size, but for a non-destructive listing tool the disclosed traits cover what an agent needs to interpret results correctly.

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 sentences, front-loaded with the resource and coverage, then the ordering and current-season marker, then the usage role. There is mild redundancy between sentence one and sentence two ('published by the results archive' / 'the formula1.com results archive publishes'), which keeps it just short of full marks.

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?

With no input schema, no annotations, and no output schema, the description is the only source of truth and it supplies ordering, coverage range, the current-season marker, and the tool's role as a parameter-discovery endpoint. The one remaining gap is whether the returned seasons are bare years or labeled objects, which an agent must discover at call time.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly spends its words on return semantics instead of inventing input guidance.

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 states a specific verb and resource ('Returns every championship season the formula1.com results archive publishes') and bounds the scope to 1950 through the current season. It also frames itself as the discovery surface for the season parameter, which meaningfully separates it from the sibling routes that consume that parameter, though it never names one explicitly.

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?

The phrase 'This is the discovery surface for the season parameter the other Formula 1 routes accept' tells the agent exactly when to reach for this tool: before calling any route that takes a season. There is no explicit when-not-to-use clause, but for a zero-parameter enumeration endpoint the implied usage is effectively unambiguous.

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