Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_odds

Fetch DraftKings Sportsbook moneyline, spread, and total betting odds for upcoming events using a numeric league_id.

Instructions

DraftKings Sportsbook odds. Returns the primary betting markets (moneyline, spread, total) for every upcoming event in a DraftKings Sportsbook league. league_id is a numeric DraftKings league identifier (find it from a league's DraftKings Sportsbook page). An empty events list is a valid response when nothing is currently scheduled.

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>"
    },
    "name": "draftkings_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
league_idYesNumeric DraftKings league id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It does disclose the returned content (moneyline, spread, total), scope (every upcoming event), and a key edge case (empty events list is valid when nothing is scheduled). It omits auth requirements, rate limits, or whether odds are live vs. cached, leaving meaningful gaps for a no-annotation tool.

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 with the core purpose front-loaded, followed by the parameter hint and the empty-response caveat. No filler, though the league_id hint is slightly redundant with the schema.

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 and no annotations, the description adequately explains what is returned, the scope of events, and the empty-result edge case. It could say more about odds freshness or pagination, but it is complete enough to invoke correctly.

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% and the single parameter is already documented as 'Numeric DraftKings league id'. The description adds mild value by restating the numeric format and explaining where to find the id, but does not add format/syntax detail beyond the schema. Baseline 3 for a high-coverage single-param schema.

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 the primary betting markets (moneyline, spread, total) for every upcoming event in a league. This is clear and concrete, but it does not name or contrast with the many sibling tools (draftkings_league_events, draftkings_event_markets) that could be confused with it.

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?

Usage is implied: use it when you have a league_id and want odds across a league's upcoming events. The only explicit guidance is how to obtain league_id (from a league's DraftKings Sportsbook page). No when-not-to-use or routing to alternatives like draftkings_event_markets or draftkings_league_events.

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