Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openf1: Get laps

openf1_get_laps
Read-onlyIdempotent

Retrieve lap timing data for a Formula 1 session, including sector times and lap durations. Filter by driver, lap number, or selected fields.

Instructions

Get lap timing data including sector times, lap duration, and more for a session.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
lap_numberNoFilter by specific lap number
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.4/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 useful context about response content (sector times, lap duration) but does not discuss authentication, rate limits, pagination, or destructive scope. It adds some value beyond the annotations without contradicting them.

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 that quickly states the verb, resource, and example data fields. 'And more' is slightly vague, but the definition is efficient and wastes little space.

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?

This is a simple read-only data-fetching tool whose annotations already cover safety. With no output schema, the description should ideally clarify the return shape, but it only gives examples and 'and more'. It is adequate but leaves response structure and pagination unspecified.

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 (fields, lap_number, session_key, driver_number) are already documented in the schema. The description adds no parameter syntax or meaning beyond loosely tying the data to a session. Baseline 3 is correct when the schema does the heavy lifting.

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 ('lap timing data') and names some returned fields (sector times, lap duration). However, it does not distinguish this tool from sibling lap-time tools such as f1_get_lap_times or nascar_get_lap_times, nor from adjacent openf1 endpoints like stints or pit. Clear but lacks sibling differentiation.

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?

No explicit when-to-use guidance, prerequisites, or alternatives are given. Usage is only implied by the returned data ('lap timing data ... for a session'), so an agent must infer that this is the right choice when lap-level timing is needed. No exclusions or sibling routing.

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