Skip to main content
Glama

SportsDataIO (Unofficial)

Sportsdataio Player Props

sportsdataio_player_props
Read-onlyIdempotent

Player prop bets for a date, available betting markets and outcomes (over/under totals, payouts) across NFL / NBA / MLB / NHL / CFB / CBB. Requires a SEPARATE SportsDataIO Odds/Props API key (the Props warehouse is billed apart from Stats/Projections). Note: a free trial key returns scrambled sample data. Example: sportsdataio_player_props({ league: "nba", date: "2026-01-15", _apiKey: "your-odds-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_player_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesSlate date in YYYY-MM-DD format, e.g. "2026-01-15"
leagueYesLeague to query. One of: nfl / nba / mlb / nhl / cfb / cbb.
_apiKeyYesSportsDataIO Odds/Props API key (separate from the Stats key)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the description's real value is the disclosure that this requires a separate Odds/Props API key billed apart from the Stats key, and that a free trial key returns scrambled sample data. That is meaningful operational context an agent cannot get from annotations. It does not describe response size or pagination behavior.

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 purpose and league scope come first, followed by the key/billing caveat and a concrete example call. Dense but front-loaded with no filler sentences; the example is somewhat redundant with the schema examples.

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, three-parameter fetch with no output schema, the description covers what data comes back (markets, outcomes, payouts), the league coverage, and the non-obvious key requirement. Remaining gaps such as response shape or rate limits are minor for this complexity level.

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 enum for league is documented, so the schema already carries the parameter meaning. The description reinforces that _apiKey must be the odds/props key rather than the stats key, which is a small but real addition; the example duplicates the schema's own examples.

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?

The description states a specific resource (player prop bets, betting markets and outcomes such as over/under totals and payouts) and the six supported leagues. It is clearly distinguishable from stats-oriented siblings like sportsdataio_projections and sportsdataio_injuries, though it never names them 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?

Usage context is implied by the resource type and the required parameters (league + slate date), but there is no explicit 'use this when...' or 'use X instead' routing. The note about needing a separate Odds/Props key is useful prerequisite guidance rather than selection guidance.

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.