Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get stints

openf1_get_stints
Read-onlyIdempotent

Retrieve Formula 1 stint data by session, including tire compound, stint number, lap counts, and tire age per driver. Filter by driver or compound.

Instructions

Get stint data including tire compound, stint number, lap counts, and tire age for each driver.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
compoundNoTire compound filter (e.g. 'SOFT', 'MEDIUM', 'HARD', 'INTERMEDIATE', 'WET')
session_keyYesSession identifier (required)
driver_numberNoFilter by driver number

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

B3.2/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 safety profile is covered. The description adds the content of the payload (per-driver stint attributes) but says nothing about pagination, scoping by session, or result ordering, so it adds only modest value beyond the structured data.

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?

A single, front-loaded sentence with no filler. It is efficient, though its brevity contributes to the missing usage context rather than the structure itself being at fault.

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?

For a simple read-only, single-session data tool with full schema coverage and existing safety annotations, the description is adequate but thin; it omits the required session_key context and any relationship to the laps/pit siblings, leaving integration decisions to inference.

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 documents fields, compound, session_key and driver_number, including the compound enum values. The description merely echoes 'tire compound' without adding format or semantics beyond what the schema provides.

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 ('Get') and resource ('stint data') and enumerates the returned fields (tire compound, stint number, lap counts, tire age). It is distinguishable from siblings like openf1_get_laps and openf1_get_pit, though it never names or contrasts with them explicitly.

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?

Provides no when-to-use guidance, no prerequisites (e.g. that it needs a session_key), and no routing to alternatives such as openf1_get_laps or openf1_get_pit. The agent must infer usage purely from the name and schema.

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