Skip to main content
Glama

GetMyHotels

by com.getmyhotels.mcp
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
refNoHotel `ref` from `search_hotels` (e.g. 'TBO:1402689'). Alternative to supplierCode + supplierHotelId.
priceYesTotal to charge for the WHOLE stay (use `grandTotal` from `get_checkout_quote` verbatim — do not multiply it by the number of nights).
roomsNoRooms (default 1).
adultsNoAdults (default 2).
checkInYesCheck-in date, ISO 8601 (YYYY-MM-DD).
checkOutYesCheck-out date, ISO 8601 (YYYY-MM-DD).
childrenNoChildren (default 0).
currencyYesISO 4217 currency of `price`/`totalPrice` (e.g. 'USD').
offerRefNoOpaque room offer from get_rooms.
roomNameYesRoom name (from the chosen room).
hotelNameYesHotel name (from `search_hotels`).
childrenAgesNoAge of each child.
supplierCodeNoSupplier code (from `search_hotels`). Required if `ref` is omitted.
supplierRoomIdNoBookable room/rate id from the chosen room in `search_hotels`.
supplierHotelIdNoSupplier hotel id (from `search_hotels`). Required if `ref` is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offerRef
      Added value: +{
+  "description": "Opaque room offer from get_rooms.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "supplierRoomId",
-  "hotelName",
-  "roomName",
-  "checkIn",
-  "checkOut",
-  "price",
-  "currency"
-]New value: +[
+  "hotelName",
+  "roomName",
+  "checkIn",
+  "checkOut",
+  "price",
+  "currency"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / price / description
      Previous value: -"Total price to charge (use `grandTotal` from `get_checkout_quote`)."New value: +"Total to charge for the WHOLE stay (use `grandTotal` from `get_checkout_quote` verbatim — do not multiply it by the number of nights)."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=false and destructiveHint=true, so the description correctly adds context beyond them: the card is not charged, the guest pays on the hosted page, and user confirmation is required beforehand. It does not disclose possible downstream effects such as holds or expiry of the checkout session, but the disclosed behavior is materially useful.

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 sentences and front-loads the primary purpose and output before adding safety and prerequisite context. Every sentence earns its place, with no redundant filler or restating of the tool name.

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 having no output schema, the description clearly states that the return value is a getmyhotels.com payment URL. The highly detailed input schema covers parameter relationships such as ref versus supplierCode/supplierHotelId. The main missing context is how this checkout differs from create_one_click_checkout, but the critical confirmation and quote-first steps are present.

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?

The input schema has 100% description coverage and already includes crucial parameter guidance, including the warning to use grandTotal verbatim and not multiply by nights. The description mostly repeats or summarizes this schema-level detail rather than adding new parameter meaning, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Create a secure checkout for a chosen hotel room" and names the concrete output: a getmyhotels.com URL. It clearly distinguishes this from the quote sibling by noting it creates the payment page rather than quoting a price, but it does not differentiate itself from the closely named sibling 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?

The description gives explicit preconditions: "Confirm the hotel, room, dates, and price with the user before calling" and "Call get_checkout_quote first to confirm the live price." It also clarifies what the tool does not do ("does NOT charge the card"), giving the agent clear context for when it is appropriate to invoke.

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

All GetMyHotels toolsInspect
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