Crawlora MCP

draftkings_casino_directory

Read-only

List the public Online Slots and How to Play Slots links from the DraftKings Casino homepage. Use it to discover the entry pages; use draftkings_casino_slots_categories for Slots section IDs, draftkings_casino_slots_guide for general rules, draftkings_casino_cleopatra_guide for Cleopatra mechanics, or draftkings_casino_wheel_of_fortune_guide for Wheel of Fortune mechanics. It excludes game listings, promotions, winners, jackpots, and account data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "draftkings_casino_directory"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds useful scoping context by enumerating what is excluded (game listings, promotions, winners, jackpots, account data), which prevents wasted calls; it does not discuss volume or ordering, but the output schema covers returns.

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 concrete scope, then the routing sentence, then the exclusions. The middle sentence is long because it enumerates four siblings, but each clause earns its place as disambiguation; nothing is redundant.

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, read-only listing tool with an output schema and safety annotations, this covers everything an agent needs: what it returns, when to prefer it, which siblings to use instead, and what it will not contain.

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 zero parameters, so there is nothing to disambiguate; the description correctly describes it as a whole-homepage directory listing with no filtering options implied.

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: list the public 'Online Slots' and 'How to Play Slots' links from the DraftKings Casino homepage. It is immediately distinguishable from the sibling guide/category tools, which it names explicitly.

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

Usage Guidelines5/5

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

Gives an explicit positive case ('use it to discover the entry pages') and routes the agent to four named alternatives with the condition each covers (Slots section IDs, general rules, Cleopatra mechanics, Wheel of Fortune mechanics). It also states what the tool does not cover.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?