Skip to main content
Glama

Strip hotel facts

hotel_info
Read-onlyIdempotent

One Las Vegas Strip hotel by name (e.g. "Bellagio", "Wynn", "Cosmopolitan", "MGM Grand"): how many rooms and when it opened, the nightclubs inside, its casino loyalty programme and hotel-chain link, whether rooms see the Grand Prix track, and the hotel's page on whatsonvegas.com. No prices: for what rooms cost on a night, use hotel_prices.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe hotel name or part of it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds useful behavioural scope beyond that: it is Strip-only, returns exactly one hotel, and deliberately omits pricing. It does not say what happens when the partial name matches nothing or matches several hotels, which is the main behavioural ambiguity left for a lookup tool.

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?

Front-loaded with the resource and scope, and every listed fact (rooms, opening date, clubs, loyalty, track views, source page) is decision-relevant for an agent choosing this tool. The single long enumerative sentence is dense and slightly hard to scan, which keeps it just below top marks.

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 correctly does the job of describing the returned fields and their source, and it flags the one thing it will not return (prices). For a one-parameter read-only lookup that is nearly complete; only no-match/multi-match behaviour is unaddressed.

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?

Schema coverage is 100% and the single parameter is already documented as 'the hotel name or part of it', so the baseline is 3. The description earns the extra point by supplying concrete example values ('Bellagio', 'Wynn', 'Cosmopolitan', 'MGM Grand') and reinforcing that matching is by name and returns a single hotel, which clarifies how loosely the string may be supplied.

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 verb (retrieve one hotel by name) and enumerates exactly what comes back: room count, opening date, nightclubs, loyalty programme, chain link, Grand Prix track views, and the whatsonvegas.com page. The scope ('Las Vegas Strip hotel', 'one ... by name') and the explicit exclusion of prices let an agent separate it from hotel_prices without opening the 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?

The closing sentence gives an explicit routing rule: no prices here, use hotel_prices for nightly rates. That is a real when/when-not statement. However, several sibling tools overlap with content this tool returns (nightlife for clubs, loyalty_tiers for programmes, whats_on for events) and none of those are differentiated, so the agent must still infer those boundaries.

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