Skip to main content
Glama

Resort loyalty status

loyalty_tiers
Read-onlyIdempotent

Status tiers of the loyalty programmes at the Las Vegas Strip resorts (MGM Rewards, Caesars Rewards, Wynn Rewards, Venetian Rewards, Genting Rewards at Resorts World): what each tier takes and includes (room rates, upgrades, resort-fee waivers, priority lines), how status is earned and reset, status matches with hotel chains and cruise lines, which resorts belong to it, sources and the date checked. Accepts a programme or a hotel name. Read-only reference information.

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": {
      "programme": "<programme>"
    },
    "name": "loyalty_tiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
programmeYesProgramme name (e.g. "Caesars Rewards", "MGM") or a Strip hotel in it (e.g. "Bellagio")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: the data includes sources and the date checked, implying a freshness/staleness caveat the agent should surface, plus the scope limit to Strip resorts.

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?

Core purpose is front-loaded in the first clause, and the remaining enumeration is all substantive content scope rather than filler. The five-programme parenthetical and 'sources and the date checked' tail make it dense, but nothing is redundant.

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?

With no output schema, the description carries the burden of describing return content and does so item by item (rates, upgrades, fee waivers, priority lines, matches, sources, date checked). Only the shape/format of the response is left unspecified, which is minor for a single-parameter reference lookup.

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?

Schema coverage is 100% and the schema description already says the argument accepts a programme name or a Strip hotel in it. The description's 'Accepts a programme or a hotel name' merely corroborates that, adding no resolution rules or fallback behavior for unknown names.

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 resource and scope: loyalty programme status tiers at named Las Vegas Strip resorts, and enumerates the content covered (earn/reset rules, matches, affiliated resorts). No sibling tool (best_nights, hotel_prices, event_details) covers this territory, so an agent can route unambiguously.

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?

Usage context is explicit ('Read-only reference information' for Strip loyalty programmes) and the acceptable input forms are stated. It stops short of naming when-not-to-use or a sibling alternative, but no sibling overlaps, so the gap is small.

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.

Resources