Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_json_drivers

Read-only

Get Formula 1 driver codes from the JSON API. Returns one season's driver dropdown: each driver's code (the value formula1-driver-season-results and the HTML standings rows use), display names, name format, avatar image and team colour codes. A season with no driver entries returns an empty list.

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

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=true and openWorldHint=true, so safety and openness are covered structurally. The description adds real value beyond them by disclosing the empty-result behavior ('A season with no driver entries returns an empty list') and that results come from the JSON API dropdown. It says nothing about rate limits, availability windows, or data freshness for an open-world call.

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 sentences, front-loaded with the action and resource, then the payload, then the empty-case edge. Every sentence carries information; the only mild cost is the dense nested parenthetical in the second sentence, which takes a moment to parse.

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?

This is a low-complexity, single-required-parameter read tool with an output schema, so return-shape detail is a bonus rather than a necessity. The description covers scope, payload, and the empty-result case, leaving only the alternative-selection guidance as an unmet need.

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?

With a single parameter at 100% schema coverage, the schema already documents the four-digit year and the 1950-through-next-season range. The description only adds the framing 'one season's driver dropdown', which is modest but consistent with the schema rather than expanding on it. 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 driver codes') and scopes it to one season's driver dropdown, listing the concrete fields returned (code, display names, name format, avatar, team colour). The parenthetical tying the code to the value used by formula1-driver-season-results and the HTML standings rows is a genuinely distinguishing detail. It stops short of naming which sibling to use instead (openf1_drivers, formula1_driver), so it is clear but not fully differentiated.

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 only implied: an agent can infer this is the tool to reach for when it needs driver codes as join keys for season results or standings. There is no explicit when-to-use/when-not statement and no named alternative among the many driver-related siblings (openf1_drivers, formula1_driver, formula1_driver_grid).

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