Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

formula1_json_editorial

Fetch official Formula 1 editorial JSON by season and resource—event listings, drivers, constructors, race calendar, or results archive—exactly as the API returns it.

Instructions

Formula 1 editorial JSON resources. Returns one editorial resource exactly as the API sends it: the season event listing (every round with its event slug, official name, circuit facts and dates), the driver listing, the constructor listing, the atom race calendar (meeting dates with city and timezone) or the results archive metadata. The resource is a closed set; every resource except race-calendar requires a season, and race-calendar rejects one.

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": {
      "resource": "<resource>"
    },
    "name": "formula1_json_editorial"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoFour-digit championship year; required for events, driver-listing, constructor-listing and results-archive, and not accepted for race-calendar example(2026)
resourceYesResource: events, driver-listing, constructor-listing, race-calendar or results-archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It helpfully discloses that the resource is returned verbatim as the API sends it (a raw passthrough, no normalization) and enumerates what each resource contains, but says nothing about authentication, rate limits, response size or error behavior on an invalid season/resource combination.

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?

Content is front-loaded with the purpose, then the resource payloads, then the constraints. The middle clause is a long run-on list, but every element carries information and there is no filler.

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 only two parameters and no output schema, the description compensates well by describing the shape of each returned resource. Only the passthrough/error behavior and cross-tool routing remain unaddressed, which are secondary here.

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 the season and resource semantics (including the enum) are already documented in the schema. The description restates the same conditional season requirement rather than adding format details such as how season interacts with race-calendar edge cases. Baseline 3 applies.

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 names a concrete dispatch behavior ('Returns one editorial resource exactly as the API sends it') and enumerates all five resources with their payload contents (event slug, circuit facts, city/timezone). An agent can distinguish what data this yields versus the sibling assembly/standings tools, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

It states the closed-set constraint and the conditional season rule ('every resource except race-calendar requires a season, and race-calendar rejects one'), which guides valid invocation. However, it gives no guidance on when to choose this editorial endpoint over siblings like formula1_json_drivers, formula1_json_meetings or formula1_json_race_calendar, which return overlapping data.

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