stays
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STAYS_RPS | No | Rate-limiter throttle (requests per second) | 10 |
| STAYS_MCP_MAX_RESULTS | No | Cap on returned list-view results (uncapped when unset) | |
| STAYS_MCP_DEFAULT_ADULTS | No | Default adults per search | 2 |
| STAYS_MCP_DEFAULT_SORT_BY | No | Default sort | RELEVANCE |
| STAYS_MCP_DEFAULT_CURRENCY | No | Fallback currency | USD |
| STAYS_MCP_DEFAULT_MAX_HOTELS_WITH_DETAILS | No | Default N for search_hotels_with_details (hard cap 15) | 5 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_hotelsA | Fast list-view hotel search. USE THIS FIRST to discover hotels. Returns name, price, rating, star class, amenities, check-in/out times, and an entity_key for each hotel. Prefer this over search_hotels_with_details unless the user explicitly asks for room/rate/cancellation detail. One RPC. entity_key values here are inputs to get_hotel_details. Common filter triggers:
|
| get_hotel_detailsA | Deep detail for ONE hotel. Requires entity_key from search_hotels. Returns rooms, per-OTA rate plans with prices, and cancellation policies. One RPC. For multi-hotel deep comparison use search_hotels_with_details instead. |
| search_hotels_with_detailsA | Search + parallel detail fetch for the top N hotels in one call. Use when the user wants to COMPARE rooms, rates, or cancellation policies across multiple hotels. Costs 1 + N RPCs. max_hotels is HARD-CAPPED at 15. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| when-to-deep-search | Guidance on choosing between search_hotels and search_hotels_with_details. |
| compare-hotels-in-city | Example workflow: find 5 top-rated hotels in a city and compare their rates. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Stays MCP Configuration | Defaults + env vars for the Google Hotels MCP server. |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: search_hotels for fast listing, get_hotel_details for deep single-hotel info, and search_hotels_with_details for multi-hotel comparison. No overlaps.
All tools follow a consistent verb_noun snake_case pattern: get_hotel_details, search_hotels, search_hotels_with_details. Naming is predictable.
With 3 tools covering search, detail retrieval, and combined search+details, the count is well-scoped for a hotel information server.
The tools cover the core workflows: finding hotels, getting details, and comparing. Minor gap: no filtering or sorting parameters beyond what's described, but the search tools include common filters.