Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

draftkings_casino_cleopatra_guide

Returns written gameplay sections from DraftKings Casino's public Cleopatra tutorial, excluding image-only payout tables and promotional CTAs, for informational reference—not wagering advice.

Instructions

DraftKings Cleopatra slot guide. Returns written gameplay sections from DraftKings Casino's public Cleopatra tutorial. The image-only payout table and promotional recommendation/CTA sections are omitted. This is informational page content, not wagering advice.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does useful work: it discloses what is omitted (image-only payout table, promotional/CTA sections) and frames the content as informational rather than wagering advice. It doesn't cover response shape or caching/freshness, but the exclusions are genuinely valuable context.

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 identity and return content, followed by exclusions and a disclaimer. Every sentence earns its place with no repetition.

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?

No output schema exists, so the description must explain returns, which it does at a high level (written gameplay sections, minus images and CTAs). It stops short of describing how sections are structured or titled, a minor gap for a static content tool.

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?

Zero parameters, so there is nothing to disambiguate; baseline of 4 applies. The description correctly implies a parameterless call.

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 verb and resource: returns written gameplay sections from DraftKings Casino's public Cleopatra slot tutorial. The game name distinguishes it from siblings like draftkings_casino_wheel_of_fortune_guide and draftkings_casino_slots_guide, though it doesn't explicitly name those alternatives.

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?

Usage is implied (informational content about the Cleopatra slot) but there is no explicit when-to-use or when-not-to-use guidance, and no mention of when the sibling slots_guide or wheel_of_fortune_guide would be preferable.

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