draftkingsapi-mcp

Line history of one Pick6 prop

get_pick6_line_history

Read-only

Retrieve recorded line movements for one Pick6 prop using its pickable_id, with optional filters for change type and pagination. Track how a specific prop's line has shifted over time.

Instructions

Recorded moves for one Pick6 prop (pickable_id from get_pick6_projections or get_public_board id). 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": {
      "pickable_id": "<pickable_id>"
    },
    "name": "get_pick6_line_history"
  }
}

Input Schema

Name	Required	Description
`task`	No	Optional: the user's task in one plain sentence, nothing personal. Helps the API return what fits.
`limit`	No	Rows to return, at most 100.
`cursor`	No	pagination.next_cursor from the previous page, unchanged.
`change_type`	No
`pickable_id`	Yes	The prop's pickable_id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

B3.4/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 genuinely useful context by naming the required DRAFTKINGS_API_KEY and where to obtain it, but says nothing about what a 'recorded move' row contains, ordering, or how pagination behaves despite a cursor parameter.

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 compact sentences with the core purpose front-loaded and the key requirement second. The signup URL is slightly promotional but still actionable information for an agent that lacks credentials.

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?

With no output schema and five parameters, the description should carry more of the return-value burden; it does not describe the shape of the history rows or pagination behavior. It is adequate for identifying and authenticating the call, but thin for interpreting results.

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 80%, so the schema already documents most parameters, and the baseline is 3. The description adds meaning only for pickable_id (its source), leaving change_type's enum semantics, limit, cursor, and task unexplained beyond the schema text.

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 and scope: 'Recorded moves for one Pick6 prop', which tells an agent this is a single-prop line-movement history rather than a board or projection feed. It does not explicitly contrast with close siblings like get_pick6_history or get_public_line_moves, so the differentiation is implied by 'one Pick6 prop' rather than stated.

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?

The description gives useful sourcing guidance for the required parameter ('pickable_id from get_pick6_projections or get_public_board id'), which is a real when-to-use signal. However, it never says when to prefer this over get_pick6_history or get_public_line_moves, nor any exclusions or prerequisites beyond the API key.

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