Roomza Hotel Intelligence

Show rooms

show_rooms

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description
`check_in`	No	Check-in date YYYY-MM-DD. Pass whenever the user's dates are known so card prices match those dates.
`room_ids`	Yes	Room UUIDs to display, in ranked order (best first). 1-8 rooms.
`check_out`	No	Check-out date YYYY-MM-DD.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rooms`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 18, 2026

addedOutput schema / properties / rooms / items / properties / photoSource

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "room",
+        "hotel"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Whether photoUrl shows the actual room or is a hotel-level fallback"
+}

changedOutput schema / properties / rooms / items / required

Previous value: -[
-  "id",
-  "hotelId",
-  "hotelName",
-  "location",
-  "roomLabel",
-  "roomNumber",
-  "floor",
-  "score",
-  "reviewCount",
-  "pricePerNight",
-  "priceNote",
-  "currency",
-  "photoUrl",
-  "view",
-  "bedType",
-  "sqFt",
-  "blurb",
-  "url"
-]New value: +[
+  "id",
+  "hotelId",
+  "hotelName",
+  "location",
+  "roomLabel",
+  "roomNumber",
+  "floor",
+  "score",
+  "reviewCount",
+  "pricePerNight",
+  "priceNote",
+  "currency",
+  "photoUrl",
+  "photoSource",
+  "view",
+  "bedType",
+  "sqFt",
+  "blurb",
+  "url"
+]

Changed5 schema fields changedAug 17, 2026

addedInput schema / properties / check_in

Added value: +{
+  "description": "Check-in date YYYY-MM-DD. Pass whenever the user's dates are known so card prices match those dates.",
+  "type": "string"
+}

addedInput schema / properties / check_out

Added value: +{
+  "description": "Check-out date YYYY-MM-DD.",
+  "type": "string"
+}

addedOutput schema / properties / rooms / items / properties / priceNote

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Shown in the price slot when pricePerNight is null, e.g. a prompt to provide dates"
+}

addedOutput schema / properties / rooms / items / properties / pricePerNight / description

Added value: +"Nightly price for the requested dates; null when no dates were given or no live rate exists"

changedOutput schema / properties / rooms / items / required

Previous value: -[
-  "id",
-  "hotelId",
-  "hotelName",
-  "location",
-  "roomLabel",
-  "roomNumber",
-  "floor",
-  "score",
-  "reviewCount",
-  "pricePerNight",
-  "currency",
-  "photoUrl",
-  "view",
-  "bedType",
-  "sqFt",
-  "blurb",
-  "url"
-]New value: +[
+  "id",
+  "hotelId",
+  "hotelName",
+  "location",
+  "roomLabel",
+  "roomNumber",
+  "floor",
+  "score",
+  "reviewCount",
+  "pricePerNight",
+  "priceNote",
+  "currency",
+  "photoUrl",
+  "view",
+  "bedType",
+  "sqFt",
+  "blurb",
+  "url"
+]

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "rooms": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "bedType": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "blurb": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "currency": {
+            "type": "string"
+          },
+          "floor": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "hotelId": {
+            "type": "string"
+          },
+          "hotelName": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "location": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "photoUrl": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "pricePerNight": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "reviewCount": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "roomLabel": {
+            "type": "string"
+          },
+          "roomNumber": {
+            "type": "string"
+          },
+          "score": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "sqFt": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "url": {
+            "type": "string"
+          },
+          "view": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "hotelId",
+          "hotelName",
+          "location",
+          "roomLabel",
+          "roomNumber",
+          "floor",
+          "score",
+          "reviewCount",
+          "pricePerNight",
+          "currency",
+          "photoUrl",
+          "view",
+          "bedType",
+          "sqFt",
+          "blurb",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "rooms"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already indicate readOnlyHint=true and idempotentHint=true, so the description does not need to repeat safety. It adds valuable behavioral context: the tool must be called before writing prose, cards appear first, and it shows specific content (photo, score, view, bed, price). No contradictions with annotations.

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?

The description is well-structured with the most critical rule front-loaded ('REQUIRED'). It is somewhat verbose but every sentence serves a purpose. Could be slightly more concise, but overall the structure effectively communicates mandatory usage and key details.

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?

Given the tool has 3 parameters, output schema, and annotations, the description is exceptionally complete. It covers all aspects: mandatory invocation, ordering, date handling, what each card shows, and the prohibition on asking users. No gaps remain for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all three parameters. The description adds extra meaning: room_ids must be in ranked order, best first, 1-8 rooms; explains the difference between passing dates (exact prices) vs no dates (typical from-price). This significantly enhances understanding beyond the schema.

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?

The description clearly states the tool's purpose: to display rooms as cards instead of describing them in text. It specifies the verb (show) and resource (rooms), and differentiates from sibling tools like get_hotel_rooms by mandating its use when presenting rooms to the user.

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?

The description provides explicit when-to-use guidance: 'REQUIRED whenever you present rooms' and 'whenever you are about to mention, recommend, or describe one or more specific rooms'. It also gives when-not-to-use guidance: 'NEVER ask the user whether they want to see cards'. It includes ordering and date handling instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Roomza Hotel Intelligence tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: searching, retrieving details, pricing, rooms, reviews, nearby places, user-specific actions (preferences, trips), booking, and presentation. The overlap between get_hotel and ask_about_hotel is intentional and clearly differentiated (ask is for supplementary questions), and get_hotel_rooms vs show_rooms are also distinct (list vs present).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: get_hotel, get_hotel_pricing, get_hotel_rooms, get_my_preferences, get_my_trips, get_nearby, get_recent_reviews, search_hotels, secure_room, show_rooms, add_special_request, ask_about_hotel. The only minor variation is 'ask_about_hotel' but it's still verb-based and follows the same structure.

Tool Count5/5

Twelve tools is well within the optimal range for a domain of this scope. The toolset covers the core lifecycle (search, view, price, book, add request, view trips) plus supporting functions (reviews, nearby, user preferences, presentation). No redundant or superfluous tools exist.

Completeness4/5

The toolset covers the primary hotel intelligence and booking workflow thoroughly: search, detail, pricing, rooms, booking, special requests, and user data. Slight gap: no explicit cancellation or booking modification tool, but given the server's focus on intelligence and presentation, this is a minor omission that agents can work around.

Resources

Need Help?