draftkingsapi-mcp

DFS slates

get_dfs_slates

Read-only

Retrieve DraftKings DFS slates by sport to identify available contests and slate IDs for lineup research.

Instructions

DraftKings DFS slates by sport. 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_slates"
  }
}

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.
`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.
`slate_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

B3.2/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 safety and external-data behavior are covered. The description's genuine addition is the DRAFTKINGS_API_KEY requirement with a sign-up path, which tells the agent about a setup step before invocation. It says nothing about pagination mechanics, result size, or error behavior when the key is absent, so it clears the annotation-adjusted bar without being rich.

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: purpose first, prerequisite second, with no filler. The sign-up URL is slightly promotional but functionally necessary since the key is unobtainable without it.

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

Completeness4/5

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

For a read-only list tool with no output schema, five loosely constrained parameters, and annotations covering safety, the definition supplies what an agent most needs beyond the schema: the provider and the required credential. The remaining gap is that it never characterizes the returned slate records, which matters somewhat since there is no output schema to fall back on.

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 explains task, limit, sport, and cursor. The description only echoes the sport filter and adds no meaning for slate_id, the one undocumented parameter, nor for how slate_id and sport interact. Baseline 3 is appropriate when the schema carries most of the load.

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 (DraftKings DFS slates) and the scoping dimension (by sport), which is concrete enough for an agent to know what it retrieves. It does not distinguish it from siblings like get_dfs_contests or get_dfs_players, so an agent must infer the slate/contest/player boundary itself.

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 guidance, no statement of when a slate lookup is preferable to the contest or player tools, and no note on whether sport is required in practice. The only conditional content is the API-key prerequisite, which is about authorization rather than tool selection.

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