Skip to main content
Glama

Bhutan Trips by Druk Asia

Update Booking

update_booking
Destructive

Updates the tour dates and/or entry and exit ports of an existing booking. Send only the fields to update. Prices, party size and itinerary cannot be changed here — create a new booking instead. Requires a valid Druk Asia API key (sent automatically via the x-api-key header).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "booking_ref": "<booking_ref>"
    },
    "name": "update_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_refYesBooking reference to update.
port_exit_idNoDeparture port Destination.Id. Must reference a destination where isExit = 1. See list_destinations.
port_entry_idNoArrival port Destination.Id. Must reference a destination where isEntry = 1. See list_destinations.
tour_end_dateNoTour end date in ISO date-time format, e.g. 2026-12-07T00:00:00.000Z.
tour_start_dateNoTour start date in ISO date-time format, e.g. 2026-12-01T00:00:00.000Z.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / booking_ref / minLength
      Removed value: -1
    • addedInput schema / properties / booking_ref / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
    • removedInput schema / properties / credit_card_charge
      Removed value: -{
      -  "description": "Credit card processing charge.",
      -  "type": "number"
      -}
    • removedInput schema / properties / grand_total
      Removed value: -{
      -  "description": "Grand total amount.",
      -  "type": "number"
      -}
    • removedInput schema / properties / is_trekking_group
      Removed value: -{
      -  "description": "Whether this booking is a trekking group.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / itinerary_id
      Removed value: -{
      -  "description": "Numeric itinerary ID (from list_itineraries or get_itinerary).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / member_id
      Removed value: -{
      -  "description": "Member ID. Create one first with create_member if not done yet.",
      -  "type": "string"
      -}
    • addedInput schema / properties / port_entry_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / port_entry_id / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / port_exit_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / port_exit_id / minimum
      Added value: +-9007199254740991
    • removedInput schema / properties / single_supplement_cost
      Removed value: -{
      -  "description": "Single room supplement cost.",
      -  "type": "number"
      -}
    • removedInput schema / properties / total_adult_air_ticket
      Removed value: -{
      -  "description": "Total adult air tickets.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / total_adult_pax
      Removed value: -{
      -  "description": "Total adult passengers.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / total_air_ticket_price
      Removed value: -{
      -  "description": "Total air ticket price.",
      -  "type": "number"
      -}
    • removedInput schema / properties / total_child_air_ticket
      Removed value: -{
      -  "description": "Total child air tickets.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / total_child_pax
      Removed value: -{
      -  "description": "Total child passengers.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / total_infant_air_ticket
      Removed value: -{
      -  "description": "Total infant air tickets.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / total_infant_pax
      Removed value: -{
      -  "description": "Total infant passengers.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / total_land_tour_price
      Removed value: -{
      -  "description": "Total land tour price.",
      -  "type": "number"
      -}
    • removedInput schema / properties / total_visa_cost
      Removed value: -{
      -  "description": "Total visa cost.",
      -  "type": "number"
      -}
    • removedInput schema / properties / trekking_cost
      Removed value: -{
      -  "description": "Trekking cost.",
      -  "type": "number"
      -}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is supplied. The description adds genuinely non-redundant behavior: PATCH-style partial update, which fields are immutable here, and that the API key is injected via the x-api-key header rather than an argument. It stops short of saying what 'destructive' concretely means (whether a date change triggers re-pricing or cancellation) and does not address the non-idempotent nature flagged in 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?

Four short sentences, front-loaded with scope, then calling convention, then exclusion, then auth. Nothing is repeated from the schema and no sentence is filler.

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?

For a destructive mutation with no output schema and fully documented parameters, the description covers scope, exclusions, partial-update semantics, and auth requirements. The remaining gap is outcome information: what a successful update returns and how errors on an invalid booking_ref surface.

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 each parameter already carries its own meaning, format examples, and the isEntry/isExit constraint with a pointer to list_destinations. The description only contributes the general rule that unspecified fields should be omitted, which is a small increment over the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Updates the tour dates and/or entry and exit ports of an existing booking') and scopes the operation precisely to four fields. It also names the sibling it is not (create_booking) for out-of-scope changes, so an agent can separate this from create_booking without opening either schema.

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 says when to use it (date and port changes), when not to (prices, party size, itinerary), and what the alternative is ('create a new booking instead'). It also gives the calling convention 'Send only the fields to update', which is the key usage rule for a partial-update tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources