Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

nascar: Get schedule

nascar_get_schedule
Read-onlyIdempotent

Retrieve NASCAR race schedules for a given year and series (Cup, Xfinity, Truck), with track, dates, winners, and stage details for completed races.

Instructions

Get the NASCAR race schedule for a season and series, including track, dates, winners and stage info for completed races.

Input Schema

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

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. Addedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the bar is lower; the description adds value by disclosing the payload shape — track, dates, winners, and stage info for completed races — which matters because there is no output schema. It does not mention pagination, rate limits, or auth, so it is not exhaustive.

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?

A single sentence that front-loads the core operation and then lists supplemental return content. Every clause is informative and none is redundant with the name or title.

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, the description usefully enumerates the returned fields (track, dates, winners, stage info) for a simple three-parameter read tool, which is most of what an agent needs. It stops short of noting result volume, ordering, or how the fields parameter narrows output.

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%: year, series_id (with the 1=Cup/2=Xfinity/3=Truck legend), and fields are all documented in the schema. The description only restates 'season and series' at a high level and adds nothing about the comma-separated fields projection, so the baseline of 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 (get the NASCAR race schedule) and scopes it precisely to a season and series, which cleanly separates it from nascar_get_lap_times and nascar_get_live. It does not name a sibling to route against, but the NASCAR-specific framing and the season/series scope make the tool's identity unambiguous.

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?

Usage is implied by 'for a season and series' and by the note that winner/stage detail applies to 'completed races', suggesting this is a past/results-oriented schedule call. There is no explicit statement of when to prefer this over nascar_get_live or a lap-times call, and no prerequisites or exclusions are given.

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