Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_json_drivers

Retrieve a Formula 1 season’s driver codes, display names, avatars, and team colors to populate driver dropdowns and match standings rows.

Instructions

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
seasonYesFour-digit championship year, 1950 through next season example(2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it identifies the data source (JSON API), enumerates the returned fields (code, display names, name format, avatar image, team colour codes), and discloses the edge case that a season with no drivers returns an empty list. It omits ordering, caching, and an explicit read-only statement, which are minor for a lookup endpoint.

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 purpose, then payload contents, then the empty-result edge case — a sensible order with little waste. Minor vagueness in phrases like 'name format' and 'team colour codes' keeps it from being maximally tight.

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?

For a one-parameter lookup with no output schema, the description covers what comes back and what happens on an empty season, which is the essential information. It could have specified the shape of the driver code itself and result ordering, but nothing critical to correct invocation is missing.

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?

There is a single parameter with 100% schema coverage, and the schema already gives the four-digit year range of 1950 through the next season. The description only reinforces the 'one season' scoping and adds nothing about format or fallback behaviour 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?

States a specific resource and scope: 'Formula 1 driver codes' for 'one season's driver dropdown.' It even links the returned code to the sibling tool formula1-driver-season-results and the HTML standings rows, so an agent can tell what the payload is for. It stops short of a fully crisp verb phrasing, but the intent is unambiguous.

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 description implies when the tool is useful by explaining that the returned code is the value consumed by formula1-driver-season-results and standings rows, which suggests a code-resolution role. It never explicitly says when to use this instead of the many sibling driver tools (openf1_drivers, formula1_driver, formula1_driver_season_results) or states prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools