GetMyHotels

Get hotel rooms

get_rooms

Read-only

List the bookable rooms for ONE hotel and date range. Each room's supplierRoomId is what you pass to get_checkout_quote / create_checkout. Use the hotel ref from search_hotels or search. Call this to see all of a chosen hotel's rooms, or to refresh availability before checkout.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	The hotel `ref` from search (e.g. 'tbo:1360717').
`rooms`	No	Rooms (default 1).
`adults`	No	Adults (default 2).
`checkIn`	Yes	Check-in date, ISO 8601 (YYYY-MM-DD).
`checkOut`	Yes	Check-out date, ISO 8601 (YYYY-MM-DD).
`children`	No	Children (default 0).
`supplierCode`	No	Alternative to `ref`: supplier code.
`supplierHotelId`	No	Alternative to `ref`: supplier hotel id.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it lists rooms and refreshes availability, aligning with read-only behavior. No contradictions and no undisclosed side effects.

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?

Two sentences front-load the core purpose and provide essential links to related tools. Every sentence is informative with no redundancy or waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description sufficiently explains inputs and how the output connects to other tools. For a simple list tool with good annotations, this is adequate but could mention the optional parameters' defaults.

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 parameters are fully documented. The description adds value by clarifying that 'ref' comes from search and that the output supplierRoomId is used in subsequent tools, enhancing semantics beyond 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 it lists bookable rooms for one hotel and date range, links the output supplierRoomId to get_checkout_quote/create_checkout, and differentiates from sibling search tools by specifying it's for a single hotel.

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?

The description provides clear context on when to use: after selecting a hotel via search_hotels or search, and to see rooms or refresh availability before checkout. It implies not to use for searching hotels but doesn't explicitly exclude alternatives.

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

All GetMyHotels 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/5.0

Disambiguation5/5

Each tool targets a distinct action or resource: searching, fetching details, checkout flows, booking management, trips, and payment methods. Overlaps like search vs search_hotels and get_booking vs get_my_booking are differentiated by input type or purpose, avoiding ambiguity.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (e.g., add_trip_item, create_checkout, get_rooms). A few exceptions like `fetch` and `search` lack a verb prefix, but they are still descriptive and fit the overall convention.

Tool Count5/5

With 18 tools, the server covers the full hotel booking lifecycle without overwhelming complexity. Each tool serves a clear purpose, and the count is well-scoped for the domain.

Completeness4/5

The tool set covers searching, viewing details, booking, checkout, cancellations, modifications, trips, and payment methods. Minor gaps exist (e.g., no delete_trip or update_payment_method), but the core workflows for booking management are complete.

Resources

Need Help?