Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_json_awards

Read-only

Get Formula 1 season awards from the JSON API. Returns one season's award dropdown: the four award labels and the absolute extension path that returns each award's per-round winners. The award values match formula1-json-season-award's award enum.

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

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.5/5.0
Behavior3/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 meaningful context by disclosing that the output is labels plus absolute extension paths rather than award winners, which prevents misuse. However, the reference to 'formula1-json-season-award's award enum' uses a non-tool-name identifier that may not map cleanly to the actual sibling, and no auth or pagination behavior is mentioned.

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?

Three tight sentences, front-loaded with the core action and followed by the return shape. No filler, though the final enum-cross-reference sentence is slightly cryptic and could be phrased more directly.

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 return values need not be spelled out, and the description still usefully summarizes them. For a single-parameter read tool with annotations, this is nearly complete; only the routing relationship to the award-detail sibling remains under-specified.

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 schema already documents the season parameter with its valid range (1950 through next season). The description adds no syntax or format detail beyond what the schema provides, 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?

States a specific verb and resource ('Get Formula 1 season awards from the JSON API') and clarifies the return shape is a dropdown of four award labels plus absolute extension paths, not the winners themselves. It references a related award enum but does not clearly distinguish itself from the siblings formula1_season_awards or formula1_json_season_award by name.

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 phrase 'returns the absolute extension path that returns each award's per-round winners' implies this is a discovery/step-one tool, but it never says explicitly 'call this first, then use formula1_json_season_award with the returned value.' No when-not or prerequisite guidance is given.

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