Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

f1: Get drivers

f1_get_drivers
Read-onlyIdempotent

List Formula 1 drivers for a given season or all-time and retrieve IDs, names, nationalities, and other details.

Instructions

List Formula 1 drivers for a given season or all-time. Returns driver IDs, names, nationalities, and other info.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 30, max 1000)
fieldsNoKeys to keep (comma-separated).
offsetNoNumber of results to skip for pagination
seasonNoSeason year (e.g. "2024") or "current" (default: "current")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
+}
    • removedInput schema / properties / offset / maximum
      Removed value: -9007199254740991
  2. Changed2 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  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=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds a partial return-shape note ('driver IDs, names, nationalities, and other info') which is useful since there is no output schema, but says nothing about pagination or default result volume beyond what the schema already documents.

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 tight sentences with zero filler, and the listing scope is front-loaded before the incidental return-field detail.

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?

For a read-only list tool with a fully documented schema, the definition covers purpose, scope and rough output contents. It stops short of naming sibling alternatives or noting that results are paginated by default, but nothing critical to correct invocation 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 schema already defines limit, offset, fields and the season format including the 'current' default. The description adds only the high-level notion that season may be a specific year or all-time, which leaves the baseline of 3 appropriate.

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 ('List Formula 1 drivers') and clarifies scope ('for a given season or all-time'), so the agent knows it is a driver-listing tool rather than a results or standings tool. It does not, however, differentiate itself from close siblings like openf1_get_drivers or f1_get_driver_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 'for a given season or all-time' phrasing implies when the tool is useful, but there is no explicit guidance on when to prefer it over openf1_get_drivers, f1_get_driver_standings, or f1_get_driver_results. Usage must be inferred from context.

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