Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_futures

Fetch league-level futures markets and selections from DraftKings Sportsbook using numeric league and subcategory IDs.

Instructions

DraftKings Sportsbook futures. Returns league-level futures markets and selections for a specific DraftKings market category. league_id is a numeric DraftKings league identifier and subcategory_id is a numeric futures category identifier. An empty events list is a valid response when the category has no markets currently posted for that league.

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": {
      "league_id": "<league_id>",
      "subcategory_id": "<subcategory_id>"
    },
    "name": "draftkings_futures"
  }
}

Input Schema

NameRequiredDescriptionDefault
league_idYesNumeric DraftKings league id
subcategory_idYesNumeric DraftKings futures market subcategory id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that an empty events list is a valid response when no markets are posted, which prevents an agent from treating it as an error. However, it doesn't state the read-only nature explicitly, nor auth requirements or rate limits.

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 tight sentences, front-loaded with what the tool returns before explaining the parameters and the empty-response edge case. Efficient, though the parameter sentence overlaps with schema content already available.

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?

No output schema and no annotations, so the description must do more. It covers the return shape at a high level and the empty-list case, but leaves the agent without guidance on sourcing the required IDs or on how this tool relates to other DraftKings endpoints.

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 description coverage is 100%, so the schema already documents both parameters. The description largely restates the schema ('numeric DraftKings league identifier'), adding only marginal framing by tying subcategory_id to a 'futures category'. Baseline 3 is appropriate.

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 states a specific verb and resource: returns league-level futures markets and selections for a DraftKings market category. This distinguishes it conceptually from odds/event siblings, but it does not name any sibling (e.g., draftkings_event_markets, draftkings_odds) to draw the boundary explicitly. Clear purpose, no sibling differentiation.

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 and no comparison to the many DraftKings siblings. It never explains where league_id and subcategory_id come from (presumably draftkings_leagues), nor when an agent should prefer futures over event markets or odds. Usage is only implied by the word 'futures'.

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

Deploy Server

Other Tools