draftkingsapi-mcp

Player box scores

get_stats_player_games

Read-only

Retrieve player game logs by sport and season to analyze performance trends, matchups, and fantasy stats; optionally filter by team, event, or athlete.

Instructions

Player game logs for a sport and season. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up).

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": {
      "sport": "<sport>",
      "season": "<season>"
    },
    "name": "get_stats_player_games"
  }
}

Input Schema

Name	Required	Description
`task`	No	Optional: the user's task in one plain sentence, nothing personal. Helps the API return what fits.
`after`	No	pagination.next / next_after from the previous page, or 'latest'.
`limit`	No	Rows to return, at most 200.
`sport`	Yes
`season`	Yes	Season year, for example 2026.
`team_id`	No
`event_id`	No
`athlete_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-call profile is covered. The description adds genuinely useful context the annotations do not: a required DRAFTKINGS_API_KEY and where to obtain it. It still says nothing about pagination behavior despite the 'after' parameter, result size limits, or what a log row looks like.

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?

Two short sentences with the core purpose front-loaded and the prerequisite second; nothing is redundant. The sign-up URL is slightly promotional but still actionable information for an agent blocking on auth.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter read tool with no output schema, the definition covers the essential (what it returns, required params, auth) but omits filter semantics, pagination via 'after', and the 200-row limit interactions. An agent could call it, but may misuse the three ID filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% across 8 parameters, so the description needs to compensate and does not. It mentions only sport and season, leaving team_id, event_id, and athlete_id completely unexplained in both schema and description, including whether they are mutually exclusive filters.

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 game logs') scoped to a sport and season, which is enough for an agent to know it returns per-player box score rows. However, it never distinguishes itself from the sibling get_stats_games, so an agent cannot tell from the text whether this is team-level or player-level game data without inferring from the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when to prefer this over get_stats_games or get_dfs_players, and no exclusions. The only contextual guidance is the auth prerequisite, which is a requirement rather than a usage rule.

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