draftkingsapi-mcp

DFS players and salaries

get_dfs_players

Read-only

Retrieves DraftKings DFS players with salaries and positions for a slate, helping agents build and compare lineups.

Instructions

DraftKings DFS players with salaries and positions for a slate. 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_dfs_players"
  }
}

Input Schema

Name	Required	Description
`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
`slate_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 and openWorldHint, so the safety profile is covered. The description usefully adds an authentication prerequisite (DRAFTKINGS_API_KEY, free, sign-up URL), which is real behavior beyond the annotations, but says nothing about pagination despite a cursor parameter or about how many rows typically come back.

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 the resource and followed by the prerequisite. The sign-up URL is slightly promotional but earns its place by unblocking a caller with no key.

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 seven optional parameters, no output schema and only moderate schema descriptions, the definition is minimally adequate: it tells you what the data is and what credential you need, but leaves scoping, filtering and pagination behavior for the agent to guess.

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 coverage is only 57% and the description adds no meaning for any of the seven parameters: team, search, slate_id and task remain unexplained, and the interaction between limit and cursor for pagination is never mentioned. 'For a slate' weakly implies slate_id matters but gives no format or requirement detail.

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 the resource concretely (DraftKings DFS players), the fields returned (salaries and positions) and the scoping unit (a slate), which separates it from siblings like get_dfs_slates and get_dfs_contests. It is a noun phrase rather than an explicit verb, but the intent is unambiguous.

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 or when-not-to-use guidance and no pointer to a sibling (e.g., use get_dfs_slates first to find a slate_id). The phrase 'for a slate' hints at the scoping but never says whether slate_id is effectively required.

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