Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get drivers

openf1_get_drivers
Read-onlyIdempotent

Retrieve Formula 1 driver details, including names, car numbers, and team names, for a specific session or across sessions.

Instructions

Get driver information for a session or across sessions. Returns driver names, numbers, team names, and more.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
session_keyNoSession identifier to get drivers for a specific session
name_acronymNoThree-letter driver acronym (e.g. 'VER', 'HAM', 'LEC')
driver_numberNoDriver's car number (e.g. 1 for Verstappen, 44 for Hamilton)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safe-read profile is covered structurally. The description adds the session-scoping behavior and a sketch of the payload, but says nothing about pagination, ordering, or coverage gaps (e.g. missing drivers for sessions without data).

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?

Two short sentences, zero filler, front-loaded with the core action and scope before the return summary. Nothing redundant or padded.

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?

With no output schema, the description rightly summarizes return content (names, numbers, team names), giving an agent enough to know whether the call answers its question. The trailing 'and more' is vague but the essentials are covered for a simple optional-filter list 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%, so all four parameters are already documented in the schema. The description adds only the session-scope hint, which the session_key schema description also conveys, 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?

States a specific verb and resource ('Get driver information') plus scope ('for a session or across sessions'). It does not differentiate from the near-identical sibling f1_get_drivers (a different provider), so an agent cannot tell which F1 driver endpoint to prefer from the description alone.

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?

Implies usage via 'for a session or across sessions' — supplying session_key narrows to one session, omitting it spans all. However, it names no alternative and gives no explicit when-to-use/when-not guidance, so the routing decision is left to inference.

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