GetMyHotels

Get checkout quote

get_checkout_quote

Read-only

Re-price a specific room live against the supplier before checkout (no booking, no charge). Use the supplierRoomId and price/currency from search_hotels. Returns the authoritative grand total, a rateValidUntil timestamp, and any taxes/fees.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	Hotel `ref` from `search_hotels` (e.g. 'TBO:1402689'). Alternative to supplierCode + supplierHotelId.
`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').
`promoCode`	No	Optional promo code.
`totalPrice`	Yes	The room's price from `search_hotels` — the TOTAL for the whole stay, not a nightly rate (used to detect price changes).
`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.4/5.0

Behavior4/5

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

Annotations provide readOnlyHint and openWorldHint. Description adds 'live against supplier', 'no booking, no charge', and mentions output fields, enhancing transparency 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, front-loaded with purpose and safety, waste-free. Efficiently communicates key information.

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?

Given 13 parameters, high schema coverage, and annotations, the description covers core behavior and return values. Could mention price comparison aspect, but overall complete.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter has a description. The description adds context by linking supplierRoomId and price/currency to search_hotels outputs, aiding correct invocation.

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 states specific verb 're-price', specific resource 'room', and distinguishes from siblings like create_checkout and search_hotels. Clearly indicates no booking or charge.

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?

Explicitly instructs to use supplierRoomId and price/currency from search_hotels, and positions tool before checkout. Lacks explicit 'when not to use' but context is clear.

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?