Skip to main content
Glama

Strip hotel prices for a night

hotel_prices
Read-onlyIdempotent

What a typical Las Vegas Strip resort room costs on a given night, against a quiet midweek night, what drives it, and whether that night is one for hotel points or cash. If the night was not sampled, returns the nearest checked nights.

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

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds real value beyond them: the baseline comparison, what drives the price, a points-vs-cash recommendation, and the fallback behavior when a date is unsampled. It stops short of describing the shape of the returned comparison.

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?

Two sentences, front-loaded with the core answer (cost of a room on a given night) before the secondary outputs and the fallback rule. Dense but every clause carries information; only 'whether that night is one for hotel points or cash' is slightly wordy.

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 one-parameter, no-output-schema tool, the description covers what is computed, the comparative framing, and the edge case of a missing sample. An agent knows enough to call it correctly and interpret an approximate answer.

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 single date parameter's YYYY-MM-DD format is documented in the schema. The description only adds that the date is interpreted as a night and may be substituted with the nearest sampled nights, which is behavioral rather than deeper semantic detail.

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?

Names a concrete resource (typical Las Vegas Strip resort room rate) and scope (a given night), plus the comparison it returns against a quiet midweek baseline. It does not explicitly distinguish itself from siblings like best_nights, so an agent must infer the split from the name alone.

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: ask for a night's price when you have a specific date in mind. The fallback rule ('if the night was not sampled, returns the nearest checked nights') is useful guidance, but there is no explicit when-not or routing to best_nights/hotel_info for the adjacent questions.

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