draftkingsapi-mcp

Game results

get_stats_games

Read-only

Fetch game results by sport and season to review outcomes and filter by event or completion status.

Instructions

Game results 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_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
`event_id`	No
`completed`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

B3.1/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 profile is covered. The description adds one genuinely useful fact beyond them — an API key is required and where to get one free — but says nothing about pagination behavior, result coverage, or what an empty result means.

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 resource statement front-loaded and the prerequisite after it. Nothing is padded, though the sign-up URL is more setup detail than tool semantics.

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

Completeness2/5

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

With no output schema and seven parameters covering filtering and pagination, the description should say what a result row contains and how paging works. It instead covers only the resource name and API-key requirement, leaving the agent to guess at filtering and return shape.

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 coverage is 43%, with task, after, and limit documented inline and sport, season, event_id, and completed undocumented. The description only restates sport and season, adding no meaning for event_id (what an event identifies) or completed (whether to restrict to finished games), so it barely compensates for the coverage gap.

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 names a specific resource and scope: 'Game results for a sport and season.' That distinguishes it well enough from the player-level sibling get_stats_player_games, but it never explicitly contrasts with it or states whether results are team-level, per-event, or final scores.

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 guidance on when to choose this over get_stats_player_games or the other stats/odds tools, and no mention of what happens without the key beyond 'needs' it. The sign-up pointer is a prerequisite, not usage guidance.

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