Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

nascar: Get lap times

nascar_get_lap_times
Read-onlyIdempotent

Retrieve per-driver NASCAR lap times and speeds for a specific race using the race_id from the schedule.

Instructions

Get per-driver lap times and speeds for a specific race. Use the race_id from nascar_get_schedule.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "series_id": "<series_id>",
      "race_id": "<race_id>"
    },
    "name": "nascar_get_lap_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesSeason year
fieldsNoKeys to keep (comma-separated).
race_idYesRace id from nascar_get_schedule
series_idYesSeries id: 1 = Cup, 2 = Xfinity, 3 = Craftsman Truck

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

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 and repeatability profile is covered. The description adds nothing beyond that – no note on volume of returned rows, pagination, or whether data exists for every race – so it clears the lowered bar but does not exceed it.

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, the core capability front-loaded, followed by the one actionable dependency. Nothing is 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?

For a read-only tool with full schema coverage, annotations and no output schema, the description covers what the tool returns and how to obtain the key identifier. The remaining gap is only the absence of any scoping detail on the returned data.

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%, including the series_id enum mapping and the year range, so the schema carries the parameter burden. The description only reinforces the race_id provenance, which the schema already states, so baseline 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 with scope: 'per-driver lap times and speeds for a specific race.' It implicitly separates itself from nascar_get_live (live vs. historical race) and f1_get_lap_times, but it does not name an alternative explicitly.

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?

Provides a prerequisite chain by telling the agent to use the race_id from nascar_get_schedule, which is genuine usage guidance. However, it gives no when-not conditions and does not contrast with nascar_get_live or f1_get_lap_times, leaving selection largely inferred.

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