Hotelumo Hotel Operations

Check room and housekeeping status

list_rooms

Read-onlyIdempotent

Use this when someone asks which rooms are clean, dirty or inspected, or which are out of order or out of service. Returns each physical room's name or number, room type and hotel with its room and housekeeping status, 20 per page by default (no guest or occupant data). Not for which rooms are free on given dates.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Rooms per page, from 1 to 100; defaults to 20
`offset`	No	Rooms to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit
`hotelId`	No	Only this hotel (24 lowercase hexadecimal characters); every hotel when absent
`roomTypeId`	No	Only this room type (24 lowercase hexadecimal characters)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes	hasMore is true when another page exists; request it with offset + limit
`rooms`	Yes	Physical rooms sorted by name. Internal room ids, reservation, occupant, guest, access-control and channel data are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 28, 2026

addedInput schema / properties / hotelId / description

Added value: +"Only this hotel (24 lowercase hexadecimal characters); every hotel when absent"

addedInput schema / properties / limit / description

Added value: +"Rooms per page, from 1 to 100; defaults to 20"

addedInput schema / properties / offset / description

Added value: +"Rooms to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit"

addedInput schema / properties / roomTypeId / description

Added value: +"Only this room type (24 lowercase hexadecimal characters)"

addedOutput schema / properties / page / description

Added value: +"hasMore is true when another page exists; request it with offset + limit"

addedOutput schema / properties / rooms / description

Added value: +"Physical rooms sorted by name. Internal room ids, reservation, occupant, guest, access-control and channel data are excluded."

removedOutput schema / properties / rooms / items / properties / housekeepingStatus / $ref
```
Removed value: -"#/properties/rooms/items/properties/name"
```

addedOutput schema / properties / rooms / items / properties / housekeepingStatus / anyOf

Added value: +[
+  {
+    "$ref": "#/properties/rooms/items/properties/name/anyOf/0"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / rooms / items / properties / housekeepingStatus / description
```
Added value: +"CLEAN, DIRTY or INSPECTED"
```
removedOutput schema / properties / rooms / items / properties / status / $ref
```
Removed value: -"#/properties/rooms/items/properties/name"
```

addedOutput schema / properties / rooms / items / properties / status / anyOf

Added value: +[
+  {
+    "$ref": "#/properties/rooms/items/properties/name/anyOf/0"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / rooms / items / properties / status / description

Added value: +"AVAILABLE (in service, not a statement about occupancy), OUT_OF_ORDER or OUT_OF_SERVICE"

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the default page size of 20 and the privacy constraint that no guest or occupant data is returned. It stops short of describing pagination limits or ordering, which keeps it out of the top range.

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 tightly packed sentences: trigger condition first, return contents second, exclusion last. No filler, and the most decision-relevant information is front-loaded.

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, yet the description still summarizes the salient return shape, and it covers the filter parameters implicitly via the schema. For a read-only list tool with full annotation coverage, nothing an agent needs to select or invoke it is missing.

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 coverage is 100%, so limit/offset/hotelId/roomTypeId semantics are already fully documented in the schema. The description adds the pagination default but does not mention the hotel or room-type filters, so it neither compensates for nor extends the schema meaningfully. Baseline 3 applies.

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 (list) and resource (rooms) with the exact status dimension it exposes — clean/dirty/inspected, out of order/service. It also names what the result contains (name/number, room type, hotel, statuses), which an agent can use to differentiate it from siblings like get_hotel_availability.

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?

Gives explicit trigger conditions ('when someone asks which rooms are clean, dirty or inspected') and an explicit exclusion ('Not for which rooms are free on given dates'), which routes the agent to the availability tool for the adjacent use case.

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

All Hotelumo Hotel Operations 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?