draftkingsapi-mcp

Sportsbook events

get_sportsbook_events

Read-only

Retrieve DraftKings Sportsbook events and start times, filtered by sport, status, search, or event ID, with pagination for browsing upcoming, live, or completed games.

Instructions

DraftKings Sportsbook events and start times. 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_sportsbook_events"
  }
}

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.
`search`	No
`status`	No
`event_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=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context by declaring the DRAFTKINGS_API_KEY prerequisite and where to obtain it, but says nothing about failure behavior when the key is missing, rate limits, or pagination handling beyond the 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 short sentences, front-loaded with the data description and followed by the prerequisite. The signup URL is long but functional; nothing is redundant, though the phrasing is slightly promotional ('free key, no card').

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 read-only, open-world list tool with seven optional parameters and no output schema, the description covers the resource and the auth prerequisite but omits filter semantics and how the enumerated status or search fields behave. It is minimally adequate but leaves meaningful gaps an agent must resolve from the schema alone.

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?

With schema coverage at 57%, search, event_id, and status carry no documented meaning, and the description does not compensate for those gaps at all. It adds no information about filters, sport codes, or cursor behavior beyond what the schema already states.

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 Sportsbook events and start times'), so an agent knows what data comes back. It is a noun phrase rather than an explicit verb+resource, and it never distinguishes itself from siblings such as get_public_sportsbook or get_odds, which keeps it below a 5.

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 when-not-to, and no named alternative. The only conditional content is the API-key prerequisite, which is a setup requirement rather than usage guidance, leaving the agent to infer when to call this versus the many sibling odds/board tools.

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