draftkingsapi-mcp

Sportsbook price history

get_odds_history

Read-only

Retrieve stored DraftKings Sportsbook odds and price history for an event or offer to track line movement and compare past prices.

Instructions

Stored DraftKings Sportsbook price history for an event or offer. 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_odds_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.
`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.
`market`	No
`event_id`	No
`offer_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

C2.9/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 adds genuinely useful context beyond them: the data is stored/historical and an API key is required, with a self-serve sign-up URL and no card needed. It stops short of saying what happens with zero filters (all history? error?) or how granular the price series is.

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 sentences, purpose first, auth requirement second, zero filler. The sign-up URL is slightly promotional but is legitimately actionable setup information for the agent.

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

Completeness2/5

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

For a 7-parameter tool with no required parameters and no output schema, the description says nothing about the shape of returned history, the behavior when no filters are supplied, or the three undocumented parameters. That ambiguity is significant because an unfiltered call could return an unbounded or unusable result.

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 market, event_id, and offer_id have no schema descriptions at all. The only compensating hint is the phrase 'for an event or offer,' which loosely maps to event_id/offer_id but does not explain the market format, how task influences results, or the cursor's relationship to limit.

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?

Names a specific resource and scope: stored DraftKings Sportsbook price history, for an event or offer. The 'history' + 'stored' wording implicitly separates it from the live-quote sibling get_odds, but the description never states that distinction explicitly, so an agent must infer it.

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 exclusions, and no mention of the obvious alternative (get_odds for current prices) or get_history_coverage for availability. The agent is left to guess whether to pass event_id, offer_id, or neither.

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