Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_json_event_tracker

Read-only

Get Formula 1 event tracker: current season context and live-timing source. Returns the event tracker payload the site's own front end reads: the current season context (season year, current or next meeting key, event and season state), the current meeting's identity and dates, the live-timing and static replay base URLs, and any published race results. This is the current-event surface; the URLs it names are not fetched by any route (live timing stays out of scope).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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.7/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 genuinely useful context beyond that: it returns the same payload the site's own front end reads, and it clarifies that the named live-timing URLs are not fetched by any route, preventing an agent from expecting live timing data.

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 and then the payload breakdown; every clause carries information. The parenthetical nesting ('(season year, current or next meeting key, event and season state)') is slightly dense but not wasteful.

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 an output schema present, the description need not enumerate return fields, yet it does so compactly, and it closes the one real ambiguity (live-timing URLs are references, not fetchable data). Complete enough to call the tool correctly with no parameters and no hidden side effects.

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 tool takes zero parameters, so parameter semantics are trivially satisfied and no description content is needed here. Baseline of 4 would apply for a no-param tool; however this description spends words on payload contents that the output schema already covers, so no extra value is added on the parameter axis.

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 uses a specific verb and resource ('Get Formula 1 event tracker') and enumerates the payload's contents (season context, current meeting identity/dates, live-timing and replay base URLs, published results). It positions itself as 'the current-event surface', which helps separate it from the many results/standings siblings, though it never names an alternative 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?

Usage is implied rather than stated: an agent can infer this is the right call for 'what is the current season/event state', and the note that live timing is out of scope draws a boundary. There is no explicit when-to-use versus when-to-use-something-else guidance (e.g. versus results or meetings tools).

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