Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_casino_directory

Retrieves public Online Slots and How to Play Slots links from the DraftKings Casino homepage for quick directory access; fetch guide sections separately with the slots guide tool.

Instructions

DraftKings Casino slots directory. Returns the public Online Slots and How to Play Slots links from the DraftKings Casino homepage. Fetch the guide sections with draftkings_casino_slots_guide. It does not fetch game catalogs, promotions, winners, jackpots, or account data.

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 full burden and largely meets it: it declares exactly what is returned (two public links) and enumerates excluded content classes. It stops short of stating read-only/safety posture or whether the links are static, but for a parameterless directory read the disclosure is solid.

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?

Three short sentences, front-loaded with the return contract, then the sibling hand-off, then the exclusion list. No filler or repetition.

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?

No output schema exists, so the description must convey return values, which it does precisely (two named links). For a zero-parameter, read-only directory tool, nothing an agent needs in order to call it correctly is missing.

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 and the baseline is 4. Nothing in the description contradicts or unnecessarily restates the empty 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 concrete verb and resource — it returns the public Online Slots and How to Play Slots links from the DraftKings Casino homepage — and names the sibling tool (draftkings_casino_slots_guide) that covers the adjacent need. An agent can distinguish this directory from the deeper guide without opening either schema.

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?

Explicitly routes to draftkings_casino_slots_guide for guide sections and adds a negative-scope sentence listing what it does not fetch (catalogs, promotions, winners, jackpots, account data). Clear usage context, though it doesn't state the positive trigger condition (e.g. 'use this to discover entry points before calling the guide').

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