Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_predictions_availability

Returns the 52 region/status mappings from DraftKings Predictions' public availability map so you can check market availability by region.

Instructions

DraftKings Predictions availability map. Returns the 52 region/status mappings shown on DraftKings Predictions' public availability map. Allowed status values: all_markets_available, financial_markets_only, sports_markets_unavailable, no_markets_available. This source map is not a complete legal eligibility matrix and does not separately classify all territories or tribal land. It does not read caller location or trading/account state.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does a solid job: it states the output size (52 mappings), enumerates allowed status values, and discloses important limitations such as not being a complete legal eligibility matrix and not reading caller location or trading/account state. It does not cover authentication, rate limits, or response shape details, but for a zero-parameter public map these are minor omissions.

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?

The description is compact, front-loaded with the core purpose, and every sentence adds useful information: output size, allowed statuses, and limitations. There is no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema and no annotations, the description is complete enough. It explains what is returned, the allowed status values, and key limitations, giving an agent sufficient context to call it correctly.

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?

The tool takes no parameters, so the baseline is 4. The description does not need to explain parameter semantics and appropriately focuses on the returned data instead.

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 the 52 region/status mappings from DraftKings Predictions' public availability map. This clearly distinguishes it from sibling DraftKings predictions tools such as categories and rules, which cover different resources.

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 description gives clear context for when the tool is appropriate: querying the public availability map. It also includes a meaningful caveat that the map is not a complete legal eligibility matrix and does not read caller location or account state, which helps avoid misuse. It does not explicitly name alternative sibling tools, so it falls short of a full when-to-use/when-not/alternatives statement.

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