draftkingsapi-mcp

Pick6 lines

get_pick6_projections

Read-only

Fetches current DraftKings Pick6 lines and multipliers across leagues, with filters for sport, player, team, stat, and status to support projection analysis.

Instructions

Current DraftKings Pick6 lines with multipliers, full board, every league. 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_projections"
  }
}

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.
`team`	No
`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.
`search`	No	Player name.
`status`	No
`fresh_only`	No
`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 declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new operational context the annotations lack: it requires a DRAFTKINGS_API_KEY and tells the agent where to get a free key, which prevents a failed call. It does not mention pagination behavior, though the schema exposes a cursor.

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, front-loaded with what the tool returns, then the prerequisite. The signup URL is long but is the actionable part an agent needs. No wasted clauses, though a parenthetical would tighten the flow.

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?

There is no output schema, so the description could reasonably say more about the returned rows (fields, multiplier shape, pagination via cursor). It covers the auth prerequisite well but leaves half the parameters and the return shape unexplained for a 10-parameter tool.

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 10 parameters. The description says nothing about the undocumented ones (stat, team, status, fresh_only, pickable_id) and adds no meaning to those the schema already explains. At this coverage level the description should compensate but does not.

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?

"Current DraftKings Pick6 lines with multipliers, full board, every league" names a specific verb-adjacent resource (current lines), the platform (DraftKings Pick6), and the payload includes multipliers. The word "Current" implicitly separates it from history siblings, but no sibling is named 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 is only implied: "Current" suggests using this for live/upcoming lines rather than past data, and "full board, every league" suggests broad retrieval. There is no explicit when-to-use or when-not-to-use guidance against get_pick6_history or get_pick6_line_history.

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