Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_race_calendar

Retrieve a Formula 1 season's race calendar, including Grand Prix weekends, testing dates, event slugs, countries, and round status for scheduling or race planning.

Instructions

Formula 1 race calendar for one season. Returns the season's published calendar: every Grand Prix weekend including future rounds and pre-season testing, with the race-hub event slug, the short and official event names, the host country, the parsed weekend start and end dates, the completed marker and the championship round. The event slug is the race-hub selector and is a different slug space from the results-archive slug; winners come from the season-results route.

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_race_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoFour-digit championship year, 2018 through next season; defaults to the current season example(2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the calendar's scope, including future rounds and pre-season testing, the return fields, the completed marker, and the distinct slug space, though it does not discuss permissions, errors, or rate limits.

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?

The description is front-loaded with the core purpose, then lists the relevant return fields, and closes with important routing caveats about slug spaces and winners. Every sentence contributes useful information without padding.

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 simple one-parameter read tool without an output schema, the description is complete enough. It explains what is returned, how future and pre-season entries are handled, and how the event slug relates to sibling routes.

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?

The input schema has 100% description coverage for the single optional season parameter, including its four-digit year range and default. The description adds only the phrase 'for one season,' so it does not meaningfully extend what the schema already documents.

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 the specific verb/resource combination: it returns a Formula 1 race calendar for one season. It goes further by naming the exact fields returned and clarifying the event slug's role, so an agent can distinguish this calendar tool from race-hub and season-results tools.

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 description makes clear that this is the calendar route and that winners must come from the season-results route, while the event slug is the race-hub selector. It does not explicitly say when not to use it, but the slug and winner caveats provide practical routing guidance.

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