GetMyHotels

Create checkout

create_checkout

Destructive

Create a secure checkout for a chosen hotel room and return a getmyhotels.com URL where the guest completes payment. This does NOT charge the card — the guest pays on the hosted page. Confirm the hotel, room, dates, and price with the user before calling. Call get_checkout_quote first to confirm the live price.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	Hotel `ref` from `search_hotels` (e.g. 'TBO:1402689'). Alternative to supplierCode + supplierHotelId.
`price`	Yes	Total to charge for the WHOLE stay (use `grandTotal` from `get_checkout_quote` verbatim — do not multiply it by the number of nights).
`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).
`currency`	Yes	ISO 4217 currency of `price`/`totalPrice` (e.g. 'USD').
`roomName`	Yes	Room name (from the chosen room).
`hotelName`	Yes	Hotel name (from `search_hotels`).
`childrenAges`	No	Age of each child.
`supplierCode`	No	Supplier code (from `search_hotels`). Required if `ref` is omitted.
`supplierRoomId`	Yes	Bookable room/rate id from the chosen room in `search_hotels`.
`supplierHotelId`	No	Supplier hotel id (from `search_hotels`). Required if `ref` is omitted.

TDQS

A4.7/5.0

Behavior4/5

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

Clearly states the tool does NOT charge the card (payment is on the hosted page), which adds transparency beyond the destructiveHint annotation. No contradictions.

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 well-structured sentences with key information front-loaded: purpose, no-charge behavior, and usage guidelines. No wasted words.

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?

Covers prerequisites, behavioral transparency, and parameter usage. Could briefly mention the return value or post-checkout flow, but overall complete given the complexity and sibling tools.

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

Parameters5/5

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

Adds significant meaning beyond the schema, e.g., 'use grandTotal from get_checkout_quote verbatim' for price, and clarifies the relationship between ref and supplierCode/supplierHotelId.

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 the tool creates a secure checkout for a hotel room and returns a URL for payment, distinguishing it from siblings like get_checkout_quote and create_one_click_checkout.

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 instructs to confirm hotel details with the user before calling and to call get_checkout_quote first to confirm live price, providing clear when-to-use and prerequisite guidance.

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?