Skip to main content
Glama

Reschedule booking

reschedule_booking
Destructive

Moves a booking to a new date and time when the customer phone matches; within 24 hours of the appointment, it creates a staff request instead.

Instructions

Moves a booking. The phone must match the booking. Within 24 hours of the appointment this creates a request for staff instead.

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_id": "<booking_id>",
      "customer_phone": "<customer_phone>",
      "new_date": "<new_date>",
      "new_time": "<new_time>"
    },
    "name": "reschedule_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_dateYesDate as YYYY-MM-DD
new_timeYesLocal 24-hour time as HH:MM
booking_idYes
customer_phoneYesCustomer phone in international format, e.g. +355691234567

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is partly covered, yet the description adds genuinely non-obvious behavior: identity verification via phone match and the fact that inside 24 hours the call produces a staff request rather than an immediate reschedule. It still omits what happens to the original slot and whether the change is reversible.

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, no filler, with the action first and the two operational constraints immediately after. Every sentence carries information an agent needs before calling.

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

Completeness3/5

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

For a destructive 4-parameter mutation with no output schema, the definition explains the triggering condition but not the result shape, which is important because the 24-hour path returns a different outcome (a pending staff request). It also leaves booking_id undocumented and does not say whether the original booking is released.

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 75% and the schema already documents date/time formats and the phone format, so the baseline is 3. The description adds meaning only for customer_phone (it must match the existing booking) and says nothing about booking_id, the one undocumented parameter.

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?

"Moves a booking" gives a clear verb and resource, and the following sentences pin down that the move is to a new date/time. It is distinct enough from cancel_booking and create_booking to be selectable, but it never explicitly contrasts itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite that the phone must match the booking is a useful usage condition, and the 24-hour rule signals an outcome branch. However, there is no explicit "use this instead of X" guidance and no statement of when a reschedule is not permitted (e.g. after the appointment has passed).

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