Skip to main content
Glama

Hotelumo Hotel Operations

by com.hotelumo
OverviewDiscussionsAdmin

List your hotels

list_hotels
Read-onlyIdempotent

Use this when someone asks which hotels or properties they manage in Hotelumo, or a hotel's id is needed. Returns each hotel's id, name, currency, language and timezone, 20 per page by default (no addresses or guest data). Not for room availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHotels per page, from 1 to 100; defaults to 20
offsetNoHotels to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYeshasMore is true when another page exists; request it with offset + limit
hotelsYesHotels in the signed-in organization. Addresses, phone numbers, channel credentials, payment configuration, reminder configuration and guest data are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Hotels per page, from 1 to 100; defaults to 20"
    • addedInput schema / properties / offset / description
      Added value: +"Hotels to skip, from 0 to 10000; defaults to 0. For the next page pass offset + limit"
    • addedOutput schema / properties / hotels / description
      Added value: +"Hotels in the signed-in organization. Addresses, phone numbers, channel credentials, payment configuration, reminder configuration and guest data are excluded."
    • addedOutput schema / properties / page / description
      Added value: +"hasMore is true when another page exists; request it with offset + limit"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/safe semantics, but the description adds real value beyond them: the returned field set (id, name, currency, language, timezone), the 20-per-page default, and what is deliberately excluded (no addresses or guest data). It does not describe error or auth behavior, so it falls short of 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 short sentences ordered by importance — trigger, return shape, exclusion — with no filler and no redundancy.

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?

For a zero-required-param list tool with an output schema and full annotation coverage, the description supplies everything an agent needs: when to call it, what comes back, and what it is not for.

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?

Both parameters are fully documented in the schema (limit 1-100 default 20, offset 0-10000 with offset+limit paging guidance), so the description's mention of "20 per page by default" only restates it. With 100% schema coverage, baseline 3 is appropriate.

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 (hotels/properties the user manages) and explicitly carves out scope with "Not for room availability," separating it from get_hotel_availability and list_room_types. An agent can identify this tool's job without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger ("when someone asks which hotels... or a hotel's id is needed") and one exclusion ("Not for room availability"). It stops short of naming the alternative sibling tool to use instead, so routing still needs a small inference.

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 toolsInspect
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