Skip to main content
Glama

Reschedule booking

reschedule_booking
Destructive

Move a booking to a new start time. Caly creates the new booking (with a new UID, returned here) and notifies attendees. Find a free time with find_available_slots, passing bookingUidToReschedule.

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": {
      "bookingUid": "<bookingUid>",
      "start": "<start>"
    },
    "name": "reschedule_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYesStart time in ISO 8601, in UTC (e.g. '2026-10-01T09:00:00Z'). Pick it from find_available_slots so it is actually free.
bookingUidYesBooking UID (a string like '2NtaeaVcKfpmSZ4CthFdfk'), as returned by list_bookings or create_booking.
rescheduledByNoEmail of whoever is rescheduling. Only needed for bookings that require confirmation; the event type owner's email auto-confirms.
reschedulingReasonNoAsk the user — never choose for them. Why the booking moves; shown to attendees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reschedulingReason / description
      Previous value: -"Why the booking moves; shown to attendees."New value: +"Ask the user — never choose for them. Why the booking moves; shown to attendees."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false; the description earns credit by explaining why — a brand-new booking with a new UID is created and attendees are notified, so repeat calls do not mutate in place. It still doesn't say whether the original booking is cancelled or what happens to existing attendees/conferencing data.

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?

Three short sentences, front-loaded with the action, then the side effects, then the prerequisite. Nothing is repeated 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?

With no output schema, the description helpfully tells the agent the new booking UID is returned here, and it covers the notification side effect and the slot-finding dependency. Given full annotation and schema coverage, the remaining gap (fate of the original booking) is minor but real.

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 coverage is 100%, so all four parameters including rescheduledBy and reschedulingReason are already documented. The description adds no parameter meaning of its own; bookingUidToReschedule is a parameter of the sibling find_available_slots, not of this tool. Baseline 3 applies.

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?

States a specific verb and resource: 'Move a booking to a new start time', which an agent can distinguish from cancel_booking or reassign_booking by intent. It does not explicitly differentiate itself from the sibling request_reschedule, which an agent could plausibly confuse with it, so it stops short of a 5.

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?

Gives a concrete workflow prerequisite: find a free time with find_available_slots, passing bookingUidToReschedule — a non-obvious detail that prevents booking an occupied slot. It never says when to prefer this over request_reschedule (the requester-side flow) or when not to use it, so no exclusion guidance.

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