GetMyHotels

Search hotels

search_hotels

Read-only

Search live hotel availability for a destination and date range. Returns a price-sorted list of hotels (JSON in the text), each with a ref and its cheapest bookable room's supplierRoomId. To book: pass a room's supplierRoomId + the hotel ref to get_checkout_quote then create_checkout. For a hotel's other rooms (or a hotel not in the list), call get_rooms. Narrow with keywords (a hotel name, area, or amenities).

Input Schema

TableJSON Schema

Name	Required	Description
`rooms`	No	Rooms (1-6). Default 1.
`adults`	No	Adults (1-10). Default 2.
`checkIn`	Yes	Check-in date, ISO 8601 (YYYY-MM-DD).
`checkOut`	Yes	Check-out date, ISO 8601 (YYYY-MM-DD). Must be after check-in.
`children`	No	Children (0-6). Default 0.
`keywords`	No	Optional free-text preferences, e.g. 'beachfront pool spa'.
`destination`	Yes	City, region, or place to search (e.g. 'Paris', 'Goa', 'Lower Manhattan').
`childrenAges`	No	Age of each child at check-in. Length should equal `children`.
`guestNationality`	No	ISO 3166-1 alpha-2 guest nationality (e.g. 'US', 'GB'). Affects supplier pricing.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only and open world; description adds context about return format (JSON with ref and supplierRoomId) and booking implications. Does not contradict annotations, but could have noted pagination or rate limits. Still adds value beyond annotations.

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 plus a short flow. Purpose is front-loaded, every sentence is informative. No fluff.

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?

Despite no output schema, the description explains the return structure and how to use it in subsequent steps. Provides complete context for a search tool with 9 parameters, lacking only minor details like pagination.

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 covers 100% of parameters with descriptions. Description only adds specific guidance on using 'keywords' for narrowing. For a high-coverage schema, baseline 3 is appropriate; marginal additional value.

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?

Clearly states the verb 'search', resource 'live hotel availability', and scope 'destination and date range'. Distinguishes from siblings like get_rooms by explicitly stating when to use each.

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?

Provides explicit when-to-use (searching for hotels), when-not-to-use (for other rooms use get_rooms, for booking use get_checkout_quote then create_checkout), and alternatives, all in a clear sequence.

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?