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.5/5.0

Behavior5/5

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

Description clearly states that the tool does NOT charge the card and returns a URL for guest payment, which goes beyond annotations that only indicate destructiveHint=true. It adds critical behavioral context.

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?

Four sentences, each adding value: core action, no-charge clarification, user confirmation requirement, prerequisite call. Front-loaded and no fluff.

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

Completeness3/5

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

Given lack of output schema, description only says 'return a getmyhotels.com URL' without detailing full response structure (e.g., checkout ID, expiry). More detail on return format would improve completeness for a complex tool with 14 parameters.

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% with detailed parameter descriptions (e.g., price usage). The description adds general guidance but no new parameter-level semantics beyond what schema already provides.

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?

Description clearly states the tool creates a secure checkout for a hotel room and returns a payment URL. It distinguishes from sibling `create_one_click_checkout` by noting this does not charge the card and requires guest to pay on hosted page.

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 says to confirm hotel, room, dates, and price with user before calling, and to call `get_checkout_quote` first for live price. Also clarifies that card is not charged, setting correct expectations.

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.2/5.0

Disambiguation5/5

Each tool targets a distinct action or resource, e.g., search vs search_hotels, get_booking vs get_my_booking. No overlapping functionality; descriptions clarify subtle differences.

Naming Consistency4/5

Most tools follow verb_noun pattern (add_trip_item, cancel_booking) or get_/list_ prefixes. One outlier ('fetch') breaks the pattern slightly, but overall naming is predictable.

Tool Count5/5

18 tools cover the hotel booking domain comprehensively without being excessive. Each tool has a clear role in the workflow from search to booking to modification.

Completeness5/5

Covers all key lifecycle stages: search, details, rooms, pricing, checkout (standard and one-click), booking management (list, get, cancel, modify), payment methods, and trip saving. No obvious gaps.

Resources

Need Help?