Skip to main content
Glama

Cancel booking

cancel_booking
Destructive

Cancel a booking when the customer phone matches; within 24 hours of the appointment, submit a cancellation request for staff approval instead.

Instructions

Cancels 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>"
    },
    "name": "cancel_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
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.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds two things the annotations cannot convey: the customer_phone must match the booking (a verification precondition), and within 24 hours of the appointment the call does NOT cancel but instead files a staff request. That second point materially changes the outcome of the call and is exactly the kind of behavioral nuance descriptions should carry.

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 primary action and immediately followed by the two conditions that affect the outcome. No filler or redundant restatement of the tool name.

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 simple three-parameter mutation with no output schema, the description covers the critical behaviors: identity verification and the 24-hour escalation path. The only shortfall is the undocumented 'reason' parameter and the absence of any statement about what a successful versus escalated response looks like.

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 only 33%, and the description compensates for the most important gap by explaining that customer_phone must match the booking (a constraint not in the schema). But the optional 'reason' parameter is documented nowhere—neither in the schema nor the description—leaving one of three parameters unexplained.

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 ("Cancels a booking"), which cleanly separates it from create_booking and reschedule_booking siblings. It stops short of naming those alternatives explicitly, so it earns a 4 rather than 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 Guidelines3/5

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

Usage is implied: an agent knows to call this to cancel rather than reschedule, and the 24-hour rule hints at when this is the right choice. However there is no explicit statement of when to prefer this over reschedule_booking or how to handle a failed phone match.

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