draftkingsapi-mcp

Pick6 change history

get_pick6_history

Read-only

Retrieve every recorded Pick6 line, multiplier, and availability change, oldest first, to track how a pickable's odds and status evolved over time.

Instructions

Every recorded Pick6 line, multiplier and availability change, oldest first. Needs DRAFTKINGS_API_KEY (free key, no card, at https://draftkingsapi.com/sign-up).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pick6_history"
  }
}

Input Schema

Name	Required	Description
`stat`	No
`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 100.
`sport`	No	Sport code in upper case, for example NFL, NBA, NHL, MLB, NCAAF, NCAAB, SOCCER.
`cursor`	No	pagination.next_cursor from the previous page, unchanged.
`pickable_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, so the description's value-add is the explicit DRAFTKINGS_API_KEY requirement with a sign-up path — exactly the kind of pre-call blocker an agent needs. It also discloses result ordering (oldest first), though it says nothing about pagination behavior or result volume.

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 payload description front-loaded and the prerequisite second. The sign-up URL is slightly promotional but earns its place as the only path to a required credential.

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 a 7-parameter, paginated history tool with no output schema, the description covers what it returns and the auth requirement but omits how pagination works in practice and how the sport/pickable_id filters narrow results. Adequate minimum, with clear gaps an agent would have to resolve from the schema.

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 71%, so most parameters (after, cursor, limit, sport, task) are already documented in the schema. The description adds no parameter-level meaning of its own; it only implies temporal filtering via 'oldest first'. Baseline 3 is appropriate at this coverage level.

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?

States a specific resource (recorded Pick6 line, multiplier and availability changes) with scope ('Every recorded') and ordering ('oldest first'), which is concrete enough to distinguish it from get_pick6_line_history and get_pick6_projections. It stops short of explicitly contrasting with the similarly named sibling.

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 versus when-not guidance and no routing to alternatives such as get_pick6_line_history or get_history_coverage. The only conditional content is the API key prerequisite, which is an auth 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.