Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_seasons

Read-only

List every Formula 1 championship season formula1.com publishes and return the available four-digit years. Use this discovery tool to pick the season the other formula1 tools accept; the results archive covers 1950 through the current season, while the calendar and race hubs cover 2018 onwards. This tool takes no parameters and is one server-rendered page read.

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

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds context beyond them: zero parameters, a single server-rendered page read (a useful cost/latency hint), and asymmetric coverage windows across the endpoint family. It stops short of noting caching, rate limits, or freshness of "current season", so it is strong but not exhaustive.

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

Conciseness5/5

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

Three sentences, each carrying distinct load: what it returns, how to use it with siblings, and its operational footprint. The identification of the return value is front-loaded and nothing is repeated from the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter discovery tool with an output schema and read-only annotations, the description supplies everything an agent needs: the return shape, the selection role, the year availability boundaries, and the request cost. Nothing material is missing.

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 schema has zero parameters, which sets a baseline of 4; the description reinforces this by stating plainly that the tool takes no parameters, removing any doubt about whether a season argument is required.

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 ("List every Formula 1 championship season formula1.com publishes") plus the return shape (four-digit years), and explicitly frames itself as a discovery tool distinct from the data-fetching siblings. An agent can identify it against the many *_seasons siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this discovery tool to pick the season the other formula1 tools accept" gives explicit routing guidance, and the coverage note (archive 1950–current vs. calendar/race hubs 2018 onwards) tells the agent when a chosen year will or will not be usable downstream. That is both a when-to-use and an effective when-not-to-use constraint.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources