GetMyHotels

Modify booking

modify_booking

Destructive

Change one of the signed-in user's bookings. Requires the 6-digit verificationCode from request_booking_action_code. Special-request edits always apply. A DATE change is pushed to the hotel supplier as a cancel-and-rebook at current availability, so it only works for suppliers that support amendment — for others (and when no room is available for the new dates) it returns an error asking you to cancel and rebook instead. A date change can shift the price and issue a new confirmation; the result's supplierModifyStatus says whether the supplier reservation was actually changed (modified), simulated (simulated), or the edit stayed local (local_only, e.g. special requests only). Never promise a date change went through unless supplierModifyStatus is modified or simulated.

Input Schema

TableJSON Schema

Name	Required	Description
`checkIn`	No	New check-in date, ISO 8601 (optional).
`checkOut`	No	New check-out date, ISO 8601 (optional).
`publicId`	Yes	The booking's public id.
`specialRequests`	No	New special requests (≤2000 chars, optional).
`verificationCode`	Yes	6-digit code from `request_booking_action_code`.

TDQS

A4.9/5.0

Behavior5/5

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

Details the cancel-and-rebook mechanism for date changes, explains special-request behavior, and introduces supplierModifyStatus. Adds significant context beyond the destructiveHint annotation.

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?

Five sentences, each providing essential information. Logically ordered: purpose, prerequisite, special-request rule, date change logic, result interpretation. No waste.

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 necessary behavioral aspects and error cases. Missing explicit output structure, but for a mutation tool without output schema, the description of supplierModifyStatus partially compensates. Could mention what happens with non-date-only changes.

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 context to verificationCode (from specific sibling), specialRequests (always apply), and date parameters (implications of change). Requires no additional clarification beyond the schema descriptions.

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 first sentence clearly states the tool modifies a signed-in user's booking, with a specific verb and resource. It is distinct from siblings like cancel_booking or request_booking_action_code.

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 requires verificationCode from request_booking_action_code, explains when date changes fail (suppliers not supporting amendment) and advises to cancel and rebook instead. Provides post-condition guidance on supplierModifyStatus.

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?