Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

formula1_driver_standings

Read-only

Get one Formula 1 season's drivers' championship table and return position, driver name, three-letter code, nationality, team, points and the driver/team profile slugs. Use season in four-digit form (1950 through the current season); the table is empty before the season starts. Use the driver slug with formula1_driver and the team slug with formula1_team.

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
seasonNoOptional four-digit championship year; the results archive serves 1950 through the current season. Defaults to the current 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

A4.2/5.0
Behavior4/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 genuinely useful behavior beyond them, notably the empty-table edge case before a season begins and the fact that both driver and team profile slugs are emitted. It stops short of describing pagination or error behavior, but this endpoint has no pagination concern.

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 resource and followed by return fields, then constraints, then cross-reference guidance. Nearly every sentence earns its place, though the four-digit/range statement duplicates what the schema already says.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple single-optional-parameter read tool with an output schema, and the description still covers the valid range, default behavior, the empty-result edge case, and how to use the returned slugs downstream. Nothing an agent needs in order to call it or interpret the result 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?

Schema description coverage is 100%, so the single season parameter is already fully documented, including the four-digit format, valid range and current-season default. The description repeats that format guidance rather than adding new semantics such as how out-of-range or future seasons are handled. Baseline 3 applies when the schema carries the parameter load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 one Formula 1 season's drivers' championship table") and enumerates the returned fields, which cleanly separates it from constructors/team standings tools. An agent can identify the tool's scope without opening the schema.

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?

Gives concrete usage context: season must be four-digit, valid 1950 through the current season, and the table is empty before a season starts. It also tells the agent how to chain the returned slugs into formula1_driver and formula1_team. It does not explicitly contrast with formula1_team_standings, but the drivers'-championship framing supplies that context.

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