Skip to main content
Glama

Cancel a booking

cancel_booking
DestructiveIdempotent

Cancel a booking (confirm with your user first). Free until 24 hours before; after that, the customer texts Ryan.

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

Input Schema

NameRequiredDescriptionDefault
linkYesThe private change-or-cancel link from the customer's confirmation email (or from request_booking).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value with the confirmation requirement and the fee/timing policy, but leaves the critical post-24-hour behavior ambiguous ("the customer texts Ryan" reads as a human escalation, not a tool outcome) and says nothing about whether the cancellation is reversible or what state the booking ends in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action front-loaded and no filler. The trailing clause about the customer texting Ryan is cryptic enough that it partially fails to earn its place without further clarification.

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, single-parameter mutation with no output schema, the description covers the confirmation gate and pricing window but omits what a successful call returns or confirms, and what the agent should do for bookings inside 24 hours. Those are meaningful holes for an irreversible action.

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?

There is a single parameter with 100% schema description coverage, including where the link comes from, so the schema already does the explanatory work. The description adds no meaning beyond it, which is the baseline expectation at this coverage level.

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?

The description opens with a specific verb+resource ("Cancel a booking") that is unambiguous and clearly distinct from the sibling change_booking_time. It stops short of naming an alternative, but the action itself is unmistakable.

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?

"Confirm with your user first" is an explicit interaction prerequisite, and the 24-hour rule signals a condition under which self-service cancellation is not the right path. What is missing is the operational consequence: the description never says whether the tool refuses, charges, or still succeeds after the 24-hour mark, so the agent must guess how to act on that boundary.

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