Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_json_meetings

Read-only

Get Formula 1 meeting ids from the JSON API. Returns one season's meeting dropdown from formula1.com's own JSON API: each meeting's numeric id, name, country code and ISO country name, and which one the site marks as current. Use the id with formula1-json-results and formula1-json-meeting-datasets; the JSON API requires the site's embedded public-bundle key, which this service rediscovers on first use and refreshes when the gateway rejects it.

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": {
      "season": "<season>"
    },
    "name": "formula1_json_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonYesRequired four-digit championship year; the JSON dropdowns serve 1950 through next season.

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

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

Goes meaningfully beyond the readOnly/openWorld annotations by disclosing that the JSON API requires the site's embedded public-bundle key, that the service rediscovers it on first use, and that it refreshes it when the gateway rejects a request. That key-handling behavior is exactly the kind of operational detail an agent cannot infer from annotations; it stops short of 5 by omitting any latency or rate-limit expectations.

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, capability stated first, downstream usage and auth behavior folded in afterward. Dense but every clause carries information; nothing is padding.

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?

Only one required parameter, a full output schema, and safety annotations are present, so the description's burden is light. It covers the remaining unknowns an agent would care about: the auth key lifecycle and how to chain the result into sibling tools.

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 description coverage is 100% and the season parameter's four-digit format and 1950-through-next-season range are already documented there. The description adds no additional syntax or constraint beyond what the schema states, so the 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?

Opens with a specific verb and resource ('Get Formula 1 meeting ids from the JSON API') and enumerates the returned fields (id, name, country code, ISO country name, current marker). It implicitly distinguishes itself from the sibling formula1_meetings by stressing formula1.com's own JSON API, though it never names that alternative directly, which keeps it short of a 5.

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?

Explicitly routes the agent downstream: use the returned id with formula1-json-results and formula1-json-meeting-datasets. That is clear positive guidance, but there is no stated when-not-to-use or comparison against the non-JSON formula1_meetings sibling.

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