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

Behavior5/5

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

Goes beyond annotations by detailing that date changes are cancel-and-rebook, may shift price/confirmation, and describes supplierModifyStatus field. Complements destructiveHint and readOnlyHint with concrete behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with main action, but somewhat lengthy due to necessary detail. Every sentence earns its place, though slight trimming could be possible without losing clarity.

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

Completeness5/5

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

Covers all major behaviors including date change implications, special request handling, supplierModifyStatus interpretation. No output schema, but description compensates with detailed return field explanation.

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%, but the description adds value by linking verificationCode to request_booking_action_code and confirming special requests ≤2000 characters. Provides connections not in 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 clearly states the verb 'change' and the resource 'one of the signed-in user's bookings', distinguishing it from sibling tools like cancel_booking (different action) and get_booking (read-only).

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?

Provides explicit context: requires verificationCode from request_booking_action_code, and notes that date changes may fail for unsupported suppliers, suggesting to cancel and rebook. Lacks explicit when-not-to-use beyond the date change case but covers prerequisites well.

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?