Skip to main content
Glama

Reschedule appointment

reschedule_appointment
Destructive

Change an appointment's start time, staff member, or services while Booksy validates new slots and rejects conflicts; optionally notify the client.

Instructions

Change an appointment: a new start time, another staff member, or other services.

Without services, moves every service of the appointment by the same amount, so the first one starts at start. With services, the list replaces the appointment's services, each with its own staff member, back to back from start (default: the current start). Booksy's dry run checks the new slots first and a busy one is refused. The client hears about it only with notify_client. Booksy refuses appointments it no longer lets you change (can in get_appointment).

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": {
      "appointment_id": "<appointment_id>"
    },
    "name": "reschedule_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNoNew start, ISO 8601. Without a time zone it is the business's local time. Default: unchanged.
servicesNoReplaces the services: the full new list in order, back to back from start. Leave a service out to remove it, add one to add it. Default: unchanged.
staff_idNoNew staff member for every service, from list_staff. Default: unchanged.
notify_clientNoTell the client about the new time through Booksy. Default: false.
appointment_idYesAppointment ID from list_appointments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.5
    • addedInput schema / properties / services
      Added value: +{
      +  "description": "Replaces the services: the full new list in order, back to back from start. Leave a service out to remove it, add one to add it. Default: unchanged.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "service_id": {
      +        "description": "service_id or variant_id from list_services.",
      +        "type": "string"
      +      },
      +      "staff_id": {
      +        "description": "Staff ID from list_staff. Default: the first one who offers the service.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "service_id"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 10,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / staff_id / description
      Previous value: -"New staff member from list_staff. Default: unchanged."New value: +"New staff member for every service, from list_staff. Default: unchanged."
    • changedInput schema / properties / start / description
      Previous value: -"New start, ISO 8601. Without a time zone it is the business's local time."New value: +"New start, ISO 8601. Without a time zone it is the business's local time. Default: unchanged."
    • changedInput schema / required
      Previous value: -[
      -  "appointment_id",
      -  "start"
      -]New value: +[
      +  "appointment_id"
      +]
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false, openWorldHint=true), the description discloses important behavior: dry-run slot checks, refusal of busy slots, client notification only when notify_client is set, and the difference between shifting all services vs replacing the service list.

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?

The description is front-loaded with purpose, then explains the two main service modes, then adds dry-run and notification behavior, and closes with eligibility. It is dense but every sentence adds useful information.

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?

For a destructive reschedule tool with no output schema, the description covers the key operational details an agent needs: service replacement semantics, default start behavior, slot validation, notification gating, and eligibility checks.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: without services every service moves by the same amount; with services the list is replaced back-to-back from start, with the current start as default.

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 names a specific verb and resource: 'Change an appointment' and then enumerates the changeable aspects (start time, staff member, services). It is clearly distinct from siblings like create_appointment or cancel_appointment without needing to name them.

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?

The description gives clear operational context, including that Booksy may refuse appointments that can no longer be changed and points to get_appointment for that check. It does not explicitly compare this tool to cancel_appointment or create_appointment, so it falls just short of the top usage-guidance score.

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