Skip to main content
Glama

Compare stays

compare_stays
Read-onlyIdempotent

Puts 2 to 4 hotels side by side for the same dates. Returns per hotel the cheapest total and per night, guest score, stars, distance, free cancellation, cheapest room and board, room size, stated policies, amenities and what guests mention, plus best flags (lowest_total, best_score, closest, free_cancellation). Rows no hotel states are left out; Not stated means that hotel did not say. Reads only; each column has its own book_link. Use when the traveller asks to compare hotels or which is cheaper, closer or quieter, and answer from the rows naming the hotel. Use get_stay_details for one hotel, search_stays to find hotel_ids.

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": {
      "hotel_ids": "<hotel_ids>",
      "checkin": "<checkin>",
      "checkout": "<checkout>",
      "adults": "<adults>"
    },
    "name": "compare_stays"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoWhat distance_km is measured from, e.g. the centre or a neighbourhood name.
adultsYesNumber of adults, 1 to 8; use the same value as the search_stays call.
checkinYesCheck-in date, YYYY-MM-DD.
checkoutYesCheck-out date, YYYY-MM-DD, after checkin.
childrenNoAges of children travelling, if any, one entry per child.
currencyNoISO 4217 currency code for prices, e.g. EUR. Default USD.
hotel_idsYes2 to 4 hotel_id values from search_stays.
distance_kmNoEach hotel's distance_km from the search, in the same order as hotel_ids; enables the closest flag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, yet the description still adds real context: per-column book_link, best flags, and the 'Not stated means that hotel did not say' semantics for missing data. It stops short of covering latency, price freshness, or response ordering, keeping it at a 4.

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 action and scope, then returns, then routing guidance. The return-value sentence is dense but each clause (best flags, Not stated, book_link) carries decision-relevant information; slightly compacted rather than wasteful.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the meaning of absent values. Combined with full schema coverage and annotations, an agent has everything needed to call and interpret this correctly.

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 description coverage is 100% and each parameter is documented, so the baseline is 3. The description only echoes the 2–4 hotel and same-dates constraint already in the schema and adds no meaning about from/distance_km ordering or currency behavior.

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?

Specific verb+resource with scope: 'Puts 2 to 4 hotels side by side for the same dates.' It enumerates exactly what is compared and returned, and explicitly separates itself from get_stay_details (one hotel) and search_stays (finding ids).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger conditions ('when the traveller asks to compare hotels or which is cheaper, closer or quieter') plus named alternatives for the adjacent intents (get_stay_details for a single hotel, search_stays to obtain hotel_ids). Nothing is left to inference.

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