Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_driver_standings

Retrieve a season's Formula 1 drivers' championship standings with positions, driver names, teams, points, and linked profile data.

Instructions

Formula 1 drivers' championship standings. Returns one season's drivers' championship table: position, driver name and abbreviation, nationality, team, points, and the driver code, profile slug and standings URLs the page links to. The results archive covers 1950 through the current season.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoFour-digit championship year, 1950 through the current season; defaults to the current season example(2026)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose the return payload's fields and the 1950-to-present coverage. It says nothing about whether current-season numbers are live or final, how frequently they refresh, or whether partial rounds are included — meaningful gaps for a standings 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?

Two sentences, front-loaded with the tool's identity and followed by the returned fields; nothing is padding. The field enumeration is long but useful for deciding whether this tool answers the question without a call.

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 single-optional-parameter read tool with no output schema, the description is nearly sufficient: it establishes scope, the season range, and the shape of the returned table. The remaining omission is data freshness for the current season, which matters for this specific tool.

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 single 'season' parameter is already documented as a four-digit year with its valid range and default. The description repeats the coverage window ('1950 through the current season') but adds no formatting or edge-case guidance beyond the schema, so the baseline of 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?

The description opens with a specific verb-and-resource statement ('Formula 1 drivers' championship standings') and then enumerates exactly what the table contains: position, driver name/abbreviation, nationality, team, points, plus driver code, profile slug and standings URLs. It implicitly separates itself from team standings by saying 'drivers' championship', but it never names the sibling tool that would be the alternative, so it falls short of the top tier.

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?

Use is only implied: the reader infers this is for pulling one season's driver standings, and the schema notes the season defaults to the current year. There is no explicit when-to-use versus when to reach for team standings or a driver-specific tool, and no statement of 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