Skip to main content
Glama

F1

by io.github.pipeworx-io

Get Driver

get_driver
Read-onlyIdempotent

Look up F1 driver profile by ID. Returns name, car number, nationality, and date of birth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
driverIdYesErgast driver ID (e.g., "hamilton", "verstappen", "leclerc")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesWikipedia URL for driver
codeYesThree-letter driver code
nameYesFull driver name
numberYesPermanent car number
driver_idYesErgast driver ID
nationalityYesDriver nationality
date_of_birthYesDate of birth (ISO format)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "code": {
+      "description": "Three-letter driver code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "date_of_birth": {
+      "description": "Date of birth (ISO format)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "driver_id": {
+      "description": "Ergast driver ID",
+      "type": "string"
+    },
+    "name": {
+      "description": "Full driver name",
+      "type": "string"
+    },
+    "nationality": {
+      "description": "Driver nationality",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number": {
+      "description": "Permanent car number",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "Wikipedia URL for driver",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "driver_id",
+    "number",
+    "code",
+    "name",
+    "date_of_birth",
+    "nationality",
+    "url"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "driverId": "hamilton"
+  },
+  {
+    "driverId": "verstappen"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint. The description adds the return fields, but since an output schema exists, this information is likely redundant. No additional behavioral context beyond annotations.

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

Conciseness5/5

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

The description is a single sentence of 12 words, directly stating the purpose and return fields. It is highly concise and front-loaded with the key action.

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?

Given the simplicity of the tool (1 required parameter, no enums, output schema present), the description adequately covers the tool's purpose and output. It slightly lacks mention of prerequisites (e.g., valid driver ID) but examples in schema compensate.

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?

The schema description coverage is 100% for the driverId parameter, with clear examples. The description does not add any semantic information beyond what the schema already provides, so baseline score of 3 is appropriate.

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 clearly states the action ('Look up'), the resource ('F1 driver profile by ID'), and the specific fields returned. This distinguishes it from sibling tools like get_race_results or get_current_standings.

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 to use the tool (to look up a driver by ID) but does not provide explicit guidance on when not to use it or mention alternatives. No exclusions or contrasts with siblings.

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

All F1 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Most tools have detailed 'use when' guidance and the polymarket/entity clusters are distinguishable, but ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx/ask_pipeworx_grounded/deep_research sit close together. Many other tools (ai_visibility_check vs scan_competitor_ai_presence, bet_research vs polymarket_edges) require careful reading to keep separate.

Naming Consistency3/5

Consistent snake_case and recognizable subfamilies (ask_pipeworx*, polymarket_*, get_*) keep names readable. However the overall set mixes verb_noun (get_schedule, resolve_entity), bare verbs (remember, forget), noun phrases (recent_alerts, pipeworx_trending), and compound noun names (bet_research, polymarket_fill_risk), so there is no single predictable convention.

Tool Count2/5

35 tools is well over the 25+ threshold and spans many unrelated concerns: F1 data, universal data lookup, prediction markets, subscriptions, memory, npm scanning, and AI visibility. While a broad data platform can justify a large surface, the mix of one-off and meta tools makes this feel bloated rather than well-scoped.

Completeness2/5

For a server named F1 the surface is thin: it covers schedule, driver profiles, race results, and driver standings but lacks constructor standings, qualifying, team/circuit data, and a driver list. The surrounding Pipeworx tools provide depth in other domains, but they do not fill the F1-specific gaps.

Resources