Skip to main content
Glama

SportsDataIO (Unofficial)

Sportsdataio Projections

sportsdataio_projections
Read-onlyIdempotent

Projected player stats for a slate, fantasy points plus key projected stats per player. Daily sports (NBA / MLB / NHL / CBB) take a date; weekly sports (NFL / CFB) take season + week. Note: a free trial key returns scrambled sample data. Example: sportsdataio_projections({ league: "nba", date: "2026-01-15", _apiKey: "your-key" }) or sportsdataio_projections({ league: "nfl", season: "2025REG", week: 5, _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2026-01-15",
      "league": "nba",
      "_apiKey": "your-sportsdataio-api-key"
    },
    "name": "sportsdataio_projections"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoGame date in YYYY-MM-DD format (used for NBA/MLB/NHL/CBB), e.g. "2026-01-15"
weekNoWeek number for weekly sports (NFL/CFB), e.g. 5
leagueYesLeague to query. One of: nfl / nba / mlb / nhl / cfb / cbb.
seasonNoSeason for weekly sports (NFL/CFB), e.g. "2025REG", "2025POST", or "2025"
_apiKeyYesSportsDataIO API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is settled. The description adds two pieces of context beyond them: the per-league parameter branching behavior and the important caveat that a free trial key yields scrambled sample data rather than real projections — a genuine gotcha an agent would otherwise misread as bad data.

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?

Front-loaded with purpose, then the sport-type rule, then the trial-key warning, then examples — a sensible priority order. The two worked examples largely duplicate the schema's own `examples` array, which is mild redundancy, but the sentences themselves are tight.

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 does carry the return-shape burden and does so at a high level ('fantasy points plus key projected stats per player'), which is enough to set expectations though not enumerate fields. Combined with full schema coverage on inputs and complete annotations, an agent has what it needs to call this correctly.

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% and the schema already documents `date`, `week`, `season`, and `league` including which sports each applies to, so the description mostly restates that mapping. The inline invocation examples add minor format confidence but no semantics the schema lacks; baseline 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 states a specific verb+resource ('Projected player stats for a slate, fantasy points plus key projected stats per player') and immediately distinguishes the two query modes (daily sports take `date`; weekly sports take `season` + `week`). An agent knows exactly what it gets back and how the tool branches by league without opening the schema.

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?

It gives clear conditional guidance on which parameter set to use per sport type and warns that a free trial key returns scrambled data, which is real operational guidance. However, it never says when to reach for this tool versus adjacent ones like player props or injuries, so alternative selection is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.