Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_driver_grid

Retrieve the current Formula 1 race grid, including driver names, teams, nationalities, team colours, profile slugs, and URLs; the response also reports the season named on the page.

Instructions

The Formula 1 driver grid the site currently shows. Returns the current race grid: each driver's first and last name, team, nationality, team colour, profile slug and profile URL. The grid page has no season selector (a season query is ignored upstream), so the route describes the season the page header names and reports that season in the payload. The grid is the current race line-up and can be smaller than the standings row set, which also lists mid-season substitutes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavioral traits: the season parameter is a no-op upstream, the season is echoed back in the payload, and the grid size can differ from the standings row set. It does not discuss caching, freshness, or failure behavior when the page lacks a race weekend, which are the remaining unknowns for a site-scraping tool.

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 its return fields, then the season caveat, then the row-set distinction. There is mild repetition ('current race grid' restated after 'the site currently shows'), but no sentence is filler.

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?

There is no output schema, so listing the returned fields is essential and it is done thoroughly. The main gap is ordering and whether the payload is a stable snapshot, minor for a small fixed-size grid that needs no pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero input parameters the baseline is 4, and the description goes slightly beyond by addressing the season-query behavior even though the schema exposes no parameters. There is no additional parameter meaning to add, so this is as strong as it can reasonably be.

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?

The description opens with a specific verb+resource: 'The Formula 1 driver grid the site currently shows,' and then enumerates exactly which fields come back (first/last name, team, nationality, team colour, profile slug, profile URL). It also explicitly differentiates the row set from the standings set ('can be smaller than the standings row set, which also lists mid-season substitutes'), so an agent can separate it from formula1_driver_standings 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?

It tells the agent the operative context: this is the current race line-up, the page has no season selector, and a season query is ignored upstream, with the season instead reported in the payload. That prevents a silent misuse (trying to request a past season). It stops short of naming an explicit alternative such as 'use formula1_driver_standings for full-season rosters', leaving that inference to the agent.

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