GetMyHotels

Create one-click checkout

create_one_click_checkout

Destructive

Create a checkout for the signed-in user with a saved card pre-selected, and return a getmyhotels.com URL where they confirm + pay in one click. Does NOT charge the card — the user confirms on the hosted page. Get the savedPaymentMethodPublicId from list_payment_methods. Confirm the hotel, room, dates, and price with the user first.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	Hotel `ref` from `search_hotels` (e.g. 'TBO:1402689').
`price`	Yes	Total 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.
`checkOut`	Yes	Check-out date, ISO 8601.
`children`	No	Children (default 0).
`currency`	Yes	ISO 4217 currency (e.g. 'USD').
`offerRef`	No	Opaque room offer from get_rooms.
`roomName`	Yes	Room name.
`hotelName`	Yes	Hotel name.
`supplierCode`	No	Supplier code (if `ref` omitted).
`supplierRoomId`	No	Bookable room/rate id from `search_hotels`.
`supplierHotelId`	No	Supplier hotel id (if `ref` omitted).
`savedPaymentMethodPublicId`	Yes	Saved card `publicId` from `list_payment_methods`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / offerRef

Added value: +{
+  "description": "Opaque room offer from get_rooms.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "supplierRoomId",
-  "savedPaymentMethodPublicId",
-  "hotelName",
-  "roomName",
-  "checkIn",
-  "checkOut",
-  "price",
-  "currency"
-]New value: +[
+  "savedPaymentMethodPublicId",
+  "hotelName",
+  "roomName",
+  "checkIn",
+  "checkOut",
+  "price",
+  "currency"
+]

Changed1 schema field changedJul 28, 2026

changedInput schema / properties / price / description

Previous value: -"Total price (use `grandTotal` from `get_checkout_quote`)."New value: +"Total for the WHOLE stay (use `grandTotal` from `get_checkout_quote` verbatim — do not multiply it by the number of nights)."

First observedJul 15, 2026

TDQS

A4/5.0

Behavior3/5

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

The description adds important behavioral context beyond the annotations by stating it does NOT charge the card and that the user confirms on the hosted page. However, with `destructiveHint: true` and no output schema, it does not disclose potential side effects like reservation holds, expiry of the generated URL, or whether a checkout record is immediately created.

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?

The description is three concise sentences with no filler. The core purpose is front-loaded, followed by the critical no-charge clarification and the necessary prerequisite/confirmation steps.

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?

The description covers the essential workflow: signed-in user, saved card, return URL, no immediate charge, and user confirmation. Since there is no output schema, the mention of the returned getmyhotels.com URL is valuable, though more detail about URL expiry or follow-up steps would make it fully complete.

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 description coverage is 100%, so parameters are already well documented. The description reinforces the source for `savedPaymentMethodPublicId` and the need to confirm price, but does not add much semantic meaning beyond the structured 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 names a specific action and resource: create a one-click checkout with a saved card and return a hosted confirmation/payment URL. It clearly differentiates from sibling `create_checkout` by emphasizing the saved-card and one-click behavior.

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 actionable context: the user must be signed in, have a saved card, and the agent should obtain `savedPaymentMethodPublicId` from `list_payment_methods`. It also instructs to confirm hotel, room, dates, and price with the user first, which is strong usage guidance, though it does not explicitly name alternative tools or exclusions.

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

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

Need Help?