Roomza Hotel Intelligence

Get room rates

get_hotel_pricing

Read-onlyIdempotent

Get public room rates for a hotel (the hotel's own public rate). 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.

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_id": "<hotel_id>"
    },
    "name": "get_hotel_pricing"
  }
}

Input Schema

Name	Required	Description
`check_in`	No	Check-in date in YYYY-MM-DD format (defaults to today)
`hotel_id`	Yes	Hotel UUID (the URL slug also works)
`check_out`	No	Check-out date in YYYY-MM-DD format (defaults to tomorrow)

Output Schema

Name	Required	Description
`note`	Yes
`found`	Yes	false when the hotel is unknown
`nights`	Yes
`checkIn`	Yes
`checkOut`	Yes
`currency`	Yes
`hotelName`	Yes
`roomTypes`	Yes	Per-room-type from-prices when dates were given and live rates exist
`typicalNightlyFrom`	Yes	Hotel-level typical nightly from-price in dollars

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 2, 2026
- changedInput schema / properties / hotel_id / description
```
Previous value: -"Hotel UUID"New value: +"Hotel UUID (the URL slug also works)"
```

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "checkIn": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checkOut": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "currency": {
+      "type": "string"
+    },
+    "found": {
+      "description": "false when the hotel is unknown",
+      "type": "boolean"
+    },
+    "hotelName": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "nights": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "roomTypes": {
+      "description": "Per-room-type from-prices when dates were given and live rates exist",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "fromNightly": {
+            "description": "Nightly from-price in whole dollars, hotel's own public rate",
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "fromNightly"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "typicalNightlyFrom": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Hotel-level typical nightly from-price in dollars"
+    }
+  },
+  "required": [
+    "found",
+    "hotelName",
+    "currency",
+    "checkIn",
+    "checkOut",
+    "nights",
+    "roomTypes",
+    "typicalNightlyFrom",
+    "note"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-redundant behavior: results are 'from' prices only, there are no booking links, and omitting dates silently shifts to a different data shape. It does not discuss caching, rate limits or freshness of pricing, which would have pushed it to a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose, mode selection, exclusion plus alternative. The most decision-relevant information (what it returns and when the parameters change that) is front-loaded with no filler.

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?

An output schema exists, so return values need no prose; the description nonetheless conveys the output shape (nightly from-prices per room type) and the degraded no-dates mode. For a 3-parameter read-only tool this is complete enough to invoke correctly on the first try.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic meaning: the date pair changes the granularity from a single typical price to per-room-type nightly from-prices. It also repeats the YYYY-MM-DD format and the no-dates fallback, which the schema only vaguely hints at ('defaults to today/tomorrow').

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?

States a specific verb and resource (get public room rates for a hotel) and immediately scopes it as the hotel's own public rate rather than a negotiated or exact-room rate. This distinguishes it from siblings like get_hotel_rooms, show_rooms and secure_room without needing the schema.

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?

Explicitly routes two modes: with check_in/check_out you get nightly from-prices per room type, without dates you get a typical from-price. It also names the alternative for exact pricing and booking (secure_room) and states the exclusion (no booking links).

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?