Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_json_editorial

Read-only

Get 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.
resourceYesRequired resource: events, driver-listing, constructor-listing, race-calendar or results-archive.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavior beyond that: it states the resource is returned 'exactly as the API sends it', signaling no normalization or shaping, and it discloses the mutual-exclusion rule between season and race-calendar. Auth, rate limits, and error behavior are not addressed, keeping it below a 5.

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?

Two sentences, front-loaded with the purpose before the resource enumeration and the season rule. The long parenthetical listing of resource contents is dense but every clause maps to a distinct resource, so little is wasted.

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?

An output schema exists, so return-value shape need not be documented, and the description nonetheless characterizes each resource's payload. With only two fully documented parameters and annotations covering the safety profile, an agent has everything needed to call this correctly.

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% and both parameters already carry descriptions enumerating the resource values and the season requirement, so the description largely restates structured data. It does add a little value by naming what each resource contains, but adds no format, range, or example detail beyond the schema.

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?

States a specific verb and resource ('Get Formula 1 editorial JSON resources') and enumerates the closed set of resources with a parenthetical summary of what each contains. It is clear what the tool returns, but it never distinguishes itself from similarly named siblings such as formula1_json_drivers or formula1_json_meetings, so an agent must infer the difference from the 'editorial' framing alone.

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?

The description gives a concrete conditional rule ('every resource except race-calendar requires a season, and race-calendar rejects one'), which is real usage guidance at the parameter level. However, it offers no when-to-use guidance relative to the many sibling F1 tools, and no exclusions or prerequisites for choosing this editorial endpoint over the direct data endpoints.

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