Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get car data

openf1_get_car_data
Read-onlyIdempotent

Retrieve Formula 1 car telemetry including speed, RPM, gear, throttle, brake, and DRS; filter by session, driver, and narrow date range to control data volume.

Instructions

Get detailed car telemetry: speed, RPM, gear, throttle, brake, DRS. WARNING: This endpoint returns massive amounts of data (multiple samples per second per car). Always use date_gte and date_lte filters to limit the time window, ideally to a few seconds or a single lap.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
date_gteNoStart datetime filter (ISO 8601, e.g. '2024-03-02T14:00:00'). Highly recommended to limit data volume.
date_lteNoEnd datetime filter (ISO 8601, e.g. '2024-03-02T14:00:10'). Highly recommended to limit data volume.
speed_gteNoMinimum speed in km/h (speed>=value)
speed_lteNoMaximum speed in km/h (speed<=value)
session_keyYesSession identifier (required)
driver_numberNoFilter by driver number (highly recommended)

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent, so the safety profile is covered; the description adds the genuinely useful behavioral fact that this endpoint returns massive, high-frequency data and must be time-bounded. It doesn't discuss pagination, rate limits or response shape, which keeps it short of a 5.

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?

Three sentences, zero waste, with the warning and its remedy front-loaded after the one-line purpose. Every sentence earns its place.

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 and full schema coverage, the description supplies the one thing the structured fields can't: the data-volume hazard and how to avoid it. Minor gaps remain around return format and pagination, but nothing needed to call it correctly 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 coverage is 100% and each parameter already carries a description, including the same 'highly recommended to limit data volume' note for date filters. The description reiterates that advice and implies per-car granularity via driver_number, but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource ('Get detailed car telemetry') and enumerates the exact fields returned (speed, RPM, gear, throttle, brake, DRS), which clearly separates it from siblings like openf1_get_laps, openf1_get_stints and openf1_get_positions.

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

Usage Guidelines4/5

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

Gives explicit operational guidance: always apply date_gte and date_lte, ideally narrowed to a few seconds or a single lap. It does not name an alternative tool for coarse-grained data (e.g. laps or intervals), so the routing guidance is strong but not complete.

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