Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_event

Fetch DraftKings Sportsbook event metadata by numeric event ID, returning league, sport, teams, status, and start time without betting odds.

Instructions

DraftKings Sportsbook event. Returns one event's metadata (league id, sport id, teams, status, start time). event_id is a numeric DraftKings event identifier (find it from an event's DraftKings Sportsbook page, or from the id field of an event returned by /draftkings/sportsbook/odds). The returned league_id is accepted by /draftkings/sportsbook/odds and /draftkings/sportsbook/futures. This endpoint does not include betting markets/odds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesNumeric DraftKings event id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.9/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 full burden. It usefully discloses what is returned (metadata fields) and explicitly what is excluded (betting markets/odds), but omits auth requirements, rate limits, and failure behavior for an invalid event_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then return contents, then parameter sourcing. Four tight sentences with no filler; each earns its place.

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?

With no output schema, the description appropriately enumerates the returned metadata fields and the cross-endpoint relationship (league_id usable in odds/futures). It's nearly complete, with only minor gaps around error/edge behavior.

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 description coverage is 100%, so baseline is 3. The description adds meaningful value by clarifying that event_id is numeric and documenting exactly where to obtain it (the event page or the `id` field from the odds endpoint), beyond the schema's terse 'Numeric DraftKings event id.'

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 metadata (league id, sport id, teams, status, start time).' It also scopes the tool by noting it does not include betting markets/odds, which helps distinguish it from odds/markets siblings, though it doesn't name those siblings explicitly.

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?

Provides clear context: where to find the required event_id (the event's DraftKings Sportsbook page or the `id` field from /draftkings/sportsbook/odds). The 'does not include betting markets/odds' statement implies when NOT to use it, but no alternative tool is named explicitly.

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