Skip to main content
Glama

get_casino

Get a casino's detail including its rewards/players-club program and full tier ladder, by slug. Each tier carries confirmed_at and the ladder carries tier_ladder_freshness.state (confirmed | stale | partial | unconfirmed). An unconfirmed or stale threshold has not been checked against the program's published terms — say so rather than stating it as current fact.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_casino"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCasino slug, e.g. bellagio-nv-880e8400

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Lacking annotations, the description provides crucial behavioral traits: it specifies technical fields returned (`confirmed_at`, `tier_ladder_freshness.state`) and includes a vital operational warning about treating stale or unconfirmed data as fact.

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?

The tool description is highly dense, but every sentence provides critical information—from the requested data fields to the necessary data integrity warning—making its length justified.

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?

Given the single-parameter nature and the rich technical details of the return data (freshness states), the description is extremely complete for an agent attempting to utilize the tool safely and accurately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since the schema coverage is 100%, the primary parameter (slug) is already fully defined. The description adds contextual value regarding the *output* of the operation rather than the *input* semantics.

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?

The description clearly defines the tool's function as retrieving a casino's details, including its specific rewards program and tier ladder, by slug.

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?

While not explicitly stating 'when to use,' the tool's granular nature and reliance on the unique slug clearly position it as the retrieval method for specific casino data compared to search or list operations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.