The room-level truth layer of hospitality. Verified scores for exact hotel rooms, not just hotels.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Add a special request to one of your bookings (e.g. extra pillows, late checkout, anniversary celebration). Requires connecting your Roomza account.
The special request to add
The booking ID to add the request to (get this from get_my_trips)
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Add a special request to one of your bookings (e.g. extra pillows, late checkout, anniversary celebration). Requires connecting your Roomza account.
| Argument | Type | Description |
|---|---|---|
| request* | string | The special request to add |
| booking_id* | string | The booking ID to add the request to (get this from get_my_trips) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"booking_id",
"request"
],
"properties": {
"request": {
"type": "string",
"description": "The special request to add"
},
"booking_id": {
"type": "string",
"description": "The booking ID to add the request to (get this from get_my_trips)"
}
}
}Ask a specific question about a hotel that standard data may not answer. Uses AI with web search to find the answer. Examples: 'Does this hotel have Eiffel Tower views?', 'Is there a rooftop bar?', 'How far is it from the airport?'. Try get_hotel first; use this only when that data doesn't answer the question.
| Argument | Type | Description |
|---|---|---|
| hotel_id* | string | Hotel UUID (the URL slug also works) |
| question* | string | The specific question about the hotel |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id",
"question"
],
"properties": {
"hotel_id": {
"type": "string",
"description": "Hotel UUID (the URL slug also works)"
},
"question": {
"type": "string",
"description": "The specific question about the hotel"
}
}
}Get full details for a hotel including: Roomza Truth summary, score breakdown, top strengths, hotel character (type, vibes, best-for), nearby landmarks with distances, neighborhood, awards, amenities, and review highlights from the open web. Use hotel name, slug, or UUID as the identifier. This is the FIRST call when the user names a specific hotel ('Wynn Las Vegas') — no search_hotels needed; the name resolves directly.
| Argument | Type | Description |
|---|---|---|
| identifier* | string | Hotel name, slug, or UUID |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string",
"description": "Hotel name, slug, or UUID"
}
}
}Get public room rates for a hotel (the hotel's own public rate; booking on Roomza never costs more). Pass check_in and check_out dates (YYYY-MM-DD) to get nightly from-prices per room type. Without dates, returns the hotel's typical nightly from-price. No booking links; to price and book an exact room, use secure_room.
| Argument | Type | Description |
|---|---|---|
| check_in | string | Check-in date in YYYY-MM-DD format (defaults to today) |
| hotel_id* | string | Hotel UUID (the URL slug also works) |
| check_out | string | Check-out date in YYYY-MM-DD format (defaults to tomorrow) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id"
],
"properties": {
"check_in": {
"type": "string",
"description": "Check-in date in YYYY-MM-DD format (defaults to today)"
},
"hotel_id": {
"type": "string",
"description": "Hotel UUID (the URL slug also works)"
},
"check_out": {
"type": "string",
"description": "Check-out date in YYYY-MM-DD format (defaults to tomorrow)"
}
}
}List rooms for a hotel with individual Roomza scores, bed type, view, and floor. Pass room_number to look up a specific room.
| Argument | Type | Description |
|---|---|---|
| hotel_id* | string | Hotel UUID from search_hotels/get_hotel (the URL slug also works) |
| room_number | string | Look up a specific room by number, e.g. "434" |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id"
],
"properties": {
"hotel_id": {
"type": "string",
"description": "Hotel UUID from search_hotels/get_hotel (the URL slug also works)"
},
"room_number": {
"type": "string",
"description": "Look up a specific room by number, e.g. \"434\""
}
}
}Get your saved room preferences, standing requests, and loyalty accounts on Roomza. Requires connecting your Roomza account.
No arguments.
{
"type": "object",
"properties": {}
}Look up your upcoming and past hotel bookings/trips on Roomza. Requires connecting your Roomza account.
No arguments.
{
"type": "object",
"properties": {}
}Get nearby places (restaurants, bars, attractions, parks) and upcoming events near a hotel. Optionally filter events to a travel window with start_date / end_date.
| Argument | Type | Description |
|---|---|---|
| end_date | string | Travel end date YYYY-MM-DD -- filters events to this window |
| hotel_id* | string | Hotel UUID from search_hotels/get_hotel (the URL slug also works) |
| start_date | string | Travel start date YYYY-MM-DD -- filters events to this window |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id"
],
"properties": {
"end_date": {
"type": "string",
"description": "Travel end date YYYY-MM-DD -- filters events to this window"
},
"hotel_id": {
"type": "string",
"description": "Hotel UUID from search_hotels/get_hotel (the URL slug also works)"
},
"start_date": {
"type": "string",
"description": "Travel start date YYYY-MM-DD -- filters events to this window"
}
}
}Get verified guest reviews for a hotel, including comments and insider tips. Pass room_number to get reviews for a specific room.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Number of reviews (default 5) |
| hotel_id* | string | Hotel UUID (the URL slug also works) |
| room_number | string | Filter reviews to a specific room number, e.g. "434" |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"hotel_id"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "Number of reviews (default 5)"
},
"hotel_id": {
"type": "string",
"description": "Hotel UUID (the URL slug also works)"
},
"room_number": {
"type": "string",
"description": "Filter reviews to a specific room number, e.g. \"434\""
}
}
}DISCOVERY ONLY: search Roomza's hotel database by city, keyword, or natural language query when the user has NOT named a specific hotel. Understands hotel types (boutique, resort, luxury), vibes (romantic, trendy, quiet), traveler types (couples, families, solo), neighborhoods, and nearby landmarks. Example queries: 'boutique hotels in SoHo', 'romantic resort near the Eiffel Tower', 'pet-friendly hotel in Seattle'. Renders for the user as a full map with a multi-hotel list (so do not repeat the list in prose). NEVER use this when the user names one specific hotel (e.g. 'Wynn Las Vegas'): the map of many hotels is wrong for that. Call get_hotel with the hotel name instead, then get_hotel_rooms and show_rooms.
| Argument | Type | Description |
|---|---|---|
| city | string | Narrow results to a specific city |
| limit | integer | Max results (default 10) |
| query* | string | Hotel name, city, or keyword |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"city": {
"type": "string",
"description": "Narrow results to a specific city"
},
"limit": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "Max results (default 10)"
},
"query": {
"type": "string",
"description": "Hotel name, city, or keyword"
}
}
}Price and lock an exact room for specific dates with Room Lock. Returns the live price, cancellation policy, and a secure booking link with the room preselected. Requires connecting your Roomza account.
| Argument | Type | Description |
|---|---|---|
| guests | integer | Guest count (default 2) |
| room_id* | string | Room UUID (from show_rooms or get_hotel_rooms) |
| check_in* | string | Check-in date, YYYY-MM-DD |
| check_out* | string | Check-out date, YYYY-MM-DD |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"room_id",
"check_in",
"check_out"
],
"properties": {
"guests": {
"type": "integer",
"maximum": 8,
"minimum": 1,
"description": "Guest count (default 2)"
},
"room_id": {
"type": "string",
"description": "Room UUID (from show_rooms or get_hotel_rooms)"
},
"check_in": {
"type": "string",
"description": "Check-in date, YYYY-MM-DD"
},
"check_out": {
"type": "string",
"description": "Check-out date, YYYY-MM-DD"
}
}
}REQUIRED whenever you present rooms. Whenever you are about to mention, recommend, or describe one or more specific rooms to the user, you MUST call this tool with those room UUIDs INSTEAD of writing the rooms in text. This is mandatory even when there is only ONE matching room — show it as a single hero card, never describe a lone room in prose. Call this BEFORE writing any prose about the rooms; the cards must appear first, then a brief summary. Pass room UUIDs (from get_hotel_rooms or search results) in ranked order, best first, 1 to 8 rooms. ALWAYS pass check_in and check_out when you know the user's dates: card prices are then for those exact dates. Without dates, cards show a typical from-price that can differ a lot from any specific dates. Each card shows photo, Roomza score, view, bed, and price. NEVER ask the user whether they want to see cards or images — just call this tool.
| Argument | Type | Description |
|---|---|---|
| check_in | string | Check-in date YYYY-MM-DD. Pass whenever the user's dates are known so card prices match those dates. |
| room_ids* | array | Room UUIDs to display, in ranked order (best first). 1-8 rooms. |
| check_out | string | Check-out date YYYY-MM-DD. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"room_ids"
],
"properties": {
"check_in": {
"type": "string",
"description": "Check-in date YYYY-MM-DD. Pass whenever the user's dates are known so card prices match those dates."
},
"room_ids": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 8,
"minItems": 1,
"description": "Room UUIDs to display, in ranked order (best first). 1-8 rooms."
},
"check_out": {
"type": "string",
"description": "Check-out date YYYY-MM-DD."
}
}
}