Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_casino_slots_guide

Returns basic rules and responsible-play sections from a public casino slots guide, omitting account setup, payments, promotions, and strategy; informational only, not gambling advice.

Instructions

DraftKings Casino slots guide. Returns the public slots guide's basic rules and responsible-play sections. Account setup, payments, promotions, and strategy sections are omitted. This is informational page content, not gambling advice.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It does useful work by stating the return is public informational page content and explicitly disclaiming that it is not gambling advice, plus what content is excluded. It stops short of describing return format, size, or any access constraints.

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 what is returned, followed by exclusions and a disclaimer. No filler and no redundancy with the name.

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?

For a zero-argument content-retrieval tool with no output schema and no annotations, the description covers enough: what sections come back, what is left out, and the informational nature of the content. Only the return structure is unspecified, which is minor for a page-content endpoint.

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 the baseline is 4; the schema is empty and the description correctly does not invent any parameter discussion. Nothing is missing on this dimension.

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 resource (the DraftKings Casino slots guide) and names exactly which sections it returns: basic rules and responsible-play. The 'slots' qualifier implicitly separates it from sibling guides like draftkings_casino_wheel_of_fortune_guide and draftkings_casino_cleopatra_guide, though it never names them explicitly.

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?

The description scopes content by listing what is omitted (account setup, payments, promotions, strategy), which lets an agent infer when this page is the wrong choice. But it gives no explicit when-to-use guidance and never routes to an alternative sibling tool.

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