Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_racing_race_info

Fetch DraftKings Racing race-card and results data by race ID, including entries, horse identifiers, morning-line and live odds, and posted finish positions.

Instructions

DraftKings Racing race card and results. Returns public race-card details for one race ID from DraftKings Racing, including entries, horse identifiers, morning-line and live odds, and finish positions when posted. It excludes pools, probable payouts, bet-form IDs, real-time WebSocket requests, favorites, and participant personal names.

Input Schema

NameRequiredDescriptionDefault
race_idYesRace ID from the public Racing schedule

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior4/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, and it does disclose meaningful traits: finish positions only appear 'when posted', and real-time WebSocket data is explicitly excluded, implying a snapshot-style read. It does not mention permissions, rate limits, or freshness guarantees, which keeps it short of a 5.

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?

Two sentences, front-loaded with purpose and then the field list followed by the exclusions. Every clause carries information; nothing is redundant with the title or 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 must describe the payload, and it does so adequately (entries, identifiers, odds, finish positions). It is nearly complete for a single-parameter lookup, though it could say more about volume or ordering of entries.

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% and the single parameter is documented as 'Race ID from the public Racing schedule'. The description reinforces the one-race-ID constraint and implies where to obtain the ID, adding marginal but useful framing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (returns public race-card details for one race ID from DraftKings Racing) and enumerates the returned fields (entries, horse identifiers, morning-line and live odds, finish positions). It also carves out what it is not (pools, payouts, bet-form IDs, WebSocket streams, favorites, personal names), which separates it from adjacent DraftKings tools.

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?

The one-race-ID scope plus the exclusion list gives a clear sense of when this tool applies and when it doesn't. However, it never names a sibling (e.g. draftkings_event_markets or draftkings_racing_schedule) as the alternative for the excluded data, so routing between tools is left partly to inference.

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