Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_event_markets

Fetch a DraftKings event's betting markets and selections by event ID and market subcategory ID, returning clean JSON for odds and prop analysis.

Instructions

DraftKings Sportsbook event markets. Returns one event's betting markets and selections for a specific market category. event_id is a numeric DraftKings event identifier (find it from the id field of an event returned by /draftkings/sportsbook/odds). subcategory_id selects the market category (e.g. game lines, a player-prop category, an alternate-line category) -- find one from the subcategory_id field on a market returned by /draftkings/sportsbook/odds. An empty markets list is a valid response when the category has no markets currently posted for this event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesNumeric DraftKings event id
subcategory_idYesNumeric DraftKings market subcategory id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that an empty `markets` list is a valid response rather than an error, which prevents misdiagnosis. However, it says nothing about permissions, rate limits, pagination, or the full shape of the returned markets/selections.

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?

Front-loaded with the core purpose, then parameter sourcing, then the empty-result caveat. Every sentence earns its place, though the parenthetical category examples add slight length.

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?

Given two required params and no output schema, the description adequately conveys both input sourcing and expected return semantics including the valid-empty case. A fuller return description would be the only remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, but the description adds real meaning: where to source each id and category examples (game lines, player props, alternate lines). This goes beyond the terse schema descriptions.

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 verb and resource: returns one event's betting markets and selections for a given market category. It is clearly distinguishable from a generic odds/events feed by its category-scoped nature, though it never names sibling tools like draftkings_event or draftkings_odds directly, only their URL paths.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the concrete usage path: find event_id from an event's `id` and subcategory_id from a market's `subcategory_id` in the odds response. That gives an agent a clear prerequisite workflow. It stops short of explicit 'when not to use' guidance or naming the alternative tools.

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