Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

formula1_driver

Retrieve a Formula 1 driver profile by slug, including team, nationality, car number, birth details, and current-season and career statistics.

Instructions

One Formula 1 driver profile. Returns one driver profile: full name, team, nationality and car number, the season the statistics describe, the current-season statistics (grand prix and sprint results, points and positions) and the career statistics, plus identity facts such as date and place of birth. The nested-statistics label and value are kept as text so suffixed values such as "1 (x9)" survive unchanged.

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": {
      "driver_slug": "<driver_slug>"
    },
    "name": "formula1_driver"
  }
}

Input Schema

NameRequiredDescriptionDefault
driver_slugYesDriver profile slug from a season page or standings row, such as kimi-antonelli example(kimi-antonelli)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does valuable work by describing the return shape and one real behavioral trait – nested statistics kept as text so suffixed values such as "1 (x9)" survive. However it says nothing about invalid or unknown slugs, whether stats are scoped to the current season only, or how missing data appears.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences repeat 'one Formula 1 driver profile' and the middle sentence is a long comma-chained field list. The final sentence about text-preserved suffixed stats is the only high-value, non-redundant content and should arguably lead.

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

Completeness3/5

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

With no output schema and no annotations, the description correctly takes on the return-value job and covers it reasonably well for a one-parameter read tool. It still leaves gaps on error behavior and on whether the 'current-season' statistics are tied to a specific season parameter.

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 sole parameter's schema already gives the format and an example ('kimi-antonelli'). The description adds no syntax, sourcing, or slug-resolution detail beyond that, 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: 'One Formula 1 driver profile', then enumerates exactly what the profile contains (name, team, nationality, car number, season, current-season and career stats). An agent knows what it gets, but nothing distinguishes it from siblings such as formula1_driver_season_results or formula1_json_drivers, and the opening two sentences restate the same idea.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance at all: no mention of when to prefer this single-profile tool over the season-results, standings, or JSON driver siblings, and no prerequisites such as where a valid slug comes from. Usage must be inferred entirely from the name and the return-field list.

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