Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_race_hub

Read-only

Get one Formula 1 race weekend hub and return its JSON-LD session schedule with UTC start times, circuit length, first-Grand-Prix facts, lap count, top results, location and bounds. event_slug comes from formula1_race_calendar (for example brazil or united-arab-emirates) and is a different slug space from the results archive; season defaults to the current championship year and the hubs cover 2018 onwards. Use formula1_session_results for a session's classification.

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": {
      "event_slug": "<event_slug>"
    },
    "name": "formula1_race_hub"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional four-digit championship year; the race hubs cover 2018 through next season. Defaults to the current season.
event_slugYesRequired race-hub event slug from formula1-race-calendar, such as brazil or united-arab-emirates. This is a different slug space from the results-archive slug.

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

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the historical coverage floor (2018 onwards), the default season semantics, and the trap of reusing results-archive slugs. It stops short of saying what happens with an invalid or out-of-range slug.

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 purpose and payload, then routing and parameter caveats. The returned-field list is long and duplicates the output schema, which is the one place wording does not fully earn its place, but the two sentences otherwise carry no fluff.

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?

An output schema exists, so the return-value enumeration is redundant rather than necessary, and the essential call requirements (slug origin, slug space, season default, coverage window) are all present. The only gap is failure behavior for an unknown slug or out-of-range season.

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 parameter descriptions already carry the slug examples, the slug-space caveat, and the default season rule, so the description largely restates structured data. The added '2018 onwards' coverage bound is the main extra signal. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource ('Get one Formula 1 race weekend hub') and enumerates the payload the agent can expect (session schedule with UTC times, circuit length, lap count, top results, location, bounds). It also distinguishes itself from formula1_race_calendar (slug source) and formula1_session_results (classification), so an agent can pick it 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?

States where the required slug comes from ('event_slug comes from formula1_race_calendar'), warns about a conflicting slug space ('different slug space from the results archive'), and names the alternative for a related need ('Use formula1_session_results for a session's classification'). Coverage limits (2018 onwards) and the season default are also given, so the selection conditions are explicit.

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