DraftKings API

Native sportsbook snapshot

get_sportsbook_snapshot

Read-onlyIdempotent

Current DraftKings sportsbook lines and player props for one native scope: events, markets and selections, with the cursor to follow changes. 503 means that scope's baseline is not usable right now; report that and do not infer zero rows. Send user_request with the current task in one sentence; it is saved to the account for 35 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scope": "<scope>",
      "user_request": "<user_request>"
    },
    "name": "get_sportsbook_snapshot"
  }
}

Input Schema

Name	Required	Description
`scope`	Yes	scope_id from get_sportsbook_scopes.
`max_rows`	No	Rows to keep per list in this response, default 100. Handled here, not by the API; state.truncated says what was left out. The request is charged once either way.
`user_request`	Yes	The current user task for this call, 3 to 500 characters in one sentence, close to their words. Required on every data call, including follow-ups and pagination. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 5, 2026

changedInput schema / properties / user_request / description

Previous value: -"Optional. The task your user asked for, in one sentence. Never a filter and never required. Kept 35 days so the team can decide what to build. Leave out personal data and secrets."New value: +"The current user task for this call, 3 to 500 characters in one sentence, close to their words. Required on every data call, including follow-ups and pagination. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private."

addedInput schema / properties / user_request / minLength
```
Added value: +3
```

changedInput schema / required

Previous value: -[
-  "scope"
-]New value: +[
+  "scope",
+  "user_request"
+]

AddedNov 4, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, yet the description still adds real behavior: a cursor for following changes, the 503 baseline-unusable condition, and the fact that max_rows truncation is handled locally and the request is charged once regardless. The only soft spot is that the cursor mechanics are described vaguely ('the cursor to follow changes').

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?

Three compact sentences, front-loaded with the resource and scope before the error and provenance notes; every sentence carries operational information. Minor redundancy in restating the user_request retention period that the schema already specifies at length.

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

Completeness5/5

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

With no output schema and only three simple parameters, the description covers the essential unknowns: what is returned (events, markets, selections), how to continue (cursor), how failure manifests (503), and how truncation is signaled. An agent has enough to call this correctly and interpret the outcome.

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 100%, so the schema already documents all three parameters in depth, establishing a baseline of 3. The description adds a little extra meaning for user_request (one sentence, saved to the account for 35 days) and confirms the scope linkage, but repeats rather than extends most of what the schema already says.

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?

States a specific resource (current DraftKings sportsbook lines and player props) and an explicit scope (one native scope covering events, markets and selections). An agent can distinguish it from list-oriented siblings like get_sportsbook_events or get_sportsbook_odds, though the description never names those siblings to sharpen the contrast.

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?

It implies usage by tying scope to 'scope_id from get_sportsbook_scopes' and gives useful error guidance (503 means the baseline is unusable; do not infer zero rows). However, it gives no explicit when-to-use versus get_sportsbook_odds or get_sportsbook_events, so the routing decision is left to inference.

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

All DraftKings API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?