Skip to main content
Glama
Sign In
sportsdata-mcp

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nba_daily_lineups

Read-onlyIdempotent

Fetch projected and confirmed NBA starting lineups for any date. Input a YYYYMMDD date to get lineups for all scheduled games that day.

Instructions

Projected/confirmed starting lineups for a date's games, from the stats.nba.com JS data feed. date is YYYYMMDD.

Returns: {games:[{gameId, homeTeam, awayTeam, lineups}]} (feed shape varies)

Example: Daily lineups for a date. {"date": "20260101"}

Auth: none needed.

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": {
      "date": "<date>"
    },
    "name": "nba_daily_lineups"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate as YYYYMMDD, e.g. 20260101. Required — part of the URL path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.24.0
    • addedInput schema / properties / date / description
      Added value: +"Date as YYYYMMDD, e.g. 20260101. Required — part of the URL path."
  2. Addedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value by identifying the data source (stats.nba.com JS feed), noting the return shape with an example, and warning that the feed shape varies. It also explicitly states 'Auth: none needed.' This goes beyond what annotations provide, though it does not cover rate limits or deeper quirks.

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?

The description is concise and front-loaded with the main purpose, followed by data format, return shape, example, and auth. Each sentence contributes useful information. Minor redundancy exists between the date format in the first paragraph and the example, but overall it is well-structured and economical.

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 simple read-only tool with one parameter and no output schema, the description is adequately complete. It covers the data source, the query parameter, the return shape (with a caveat that it varies), an example, and authentication requirements. It could be slightly clearer about the difference between 'projected' and 'confirmed' lineups, but this is not a major gap given the tool's simplicity.

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 the 'date' parameter format and requirement. The description repeats the format (YYYYMMDD) and gives an example, but adds no new semantic meaning beyond what the schema provides. A baseline of 3 is appropriate.

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?

The description clearly states the tool's purpose with a specific verb and resource: 'Projected/confirmed starting lineups for a date's games.' It distinguishes this from sibling NBA tools like nba_scoreboard_today or nba_boxscore by focusing specifically on lineups.

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?

The description provides clear context for when to use the tool: for a given date's starting lineups. However, it does not explicitly mention alternative tools or exclusion criteria, so it does not earn a 5, but the usage scenario is unambiguous.

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