Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

formula1_json_race_assembly

Fetches one Formula 1 race weekend's complete editorial payload—race data, session schedule, circuit details, links, promotions, and related articles/videos—via meeting ID or season plus identifier.

Instructions

One Formula 1 race weekend's editorial assembly. Returns one race weekend's full editorial assembly payload exactly as the API sends it: the structured data (fomRaceId, season, identifier, SEO copy, brand colour and images), the session schedule (race.meetingSessions with session codes, names and UTC start/end times), the circuit description, session link sets, promotional content and the related article/video assemblies. Use either meeting or season+identifier, never both. Identifiers match the race-hub event slugs from formula1-race-calendar.

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

Input Schema

Name	Required	Description
`season`	No	Four-digit championship year for the season+identifier mode example(2026)
`meeting`	No	Numeric meeting id from formula1-json-meetings; use it alone example(1299)
`identifier`	No	Race identifier (lowercase letters, numbers, hyphens) such as brazil; required with season example(brazil)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose that the payload is returned exactly as the API sends it, plus a detailed inventory of what comes back, including nested session schedule fields (codes, names, UTC start/end times). It is implicitly a read operation ('Returns'), but it does not state permissions, rate limits, or failure behavior for unmatched identifiers.

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?

Front-loaded with the core purpose, then the return inventory, then the invocation rule, which is a sensible order. The field enumeration is dense but each item distinguishes this payload from a generic race response; nothing is obviously redundant.

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?

There is no output schema, so the description must explain returns, and it does so thoroughly, listing the major payload sections including nested session schedule data. Combined with the dual-mode invocation rule, an agent has enough to call it correctly; only edge-case behavior for invalid identifiers is unaddressed.

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 the baseline is 3. The description does add one genuine constraint beyond the schema: `meeting` and `season`+`identifier` are mutually exclusive and never combined, which the schema alone does not express since all three properties are optional and independent.

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: returns one F1 race weekend's full editorial assembly payload, and enumerates the contents (structured data, session schedule, circuit description, link sets, promo content, related articles/videos). This is far more specific than a tautology. It stops short of a clean sibling differentiation, though it does cross-reference the race-hub slugs from formula1-race-calendar.

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?

Gives explicit invocation-mode guidance: use either `meeting` or `season`+`identifier`, never both, and points to formula1-json-meetings as the source of numeric meeting ids. What is missing is tool-selection guidance, i.e. when to reach for this instead of sibling assemblies such as formula1_json_editorial or formula1_race_hub.

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

Deploy Server