Skip to main content
Glama

cancel_booking

Destructive

Irreversibly cancel a booking and calculate its policy-based refund.

Cancellation cannot be undone. If payment was captured and the policy owes a non-zero refund, this call may also initiate refund processing. Returns the refund percentage and amount. Requires OAuth2 authentication.

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

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional cancellation reason, e.g. 'Change of plans', 'Weather concerns'.
operator_idNoUnique operator slug, e.g. 'fosshotel-reykjavik' or 'arctic-adventures'. Obtain from search_operators. Do not guess — always look up first.
booking_referenceYesBooking reference code to cancel.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new context beyond them: the cancellation cannot be undone, a captured payment may trigger refund processing as a side effect, and OAuth2 authentication is required. Those are exactly the behavioral facts an agent needs before invoking a destructive tool; only rate limits or failure modes are missing.

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?

Three short sentences with the irreversible nature front-loaded ahead of refund behavior and auth. Minor redundancy: the return values are already covered by the output schema, so that sentence earns less than the rest.

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 destructive, non-idempotent mutation the description covers the critical dimensions — irreversibility, conditional refund side effect, and authentication — and an output schema exists to explain return values. It stops short of describing error conditions or what happens if the refund fails, which would complete the picture.

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 description coverage is 100%, with booking_reference, reason, and operator_id each documented in the schema (including the 'do not guess — look up via search_operators' warning). The description adds no parameter-level detail at all, so the baseline 3 applies since the schema carries the full burden.

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 plus resource ('Irreversibly cancel a booking') and adds the secondary outcome ('calculate its policy-based refund'), which separates it from siblings like create_booking and get_booking_status. It is clear what the tool does, though it never names the read-only sibling an agent might use to verify state first.

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 rather than stated: the agent learns this is the cancellation path and that a refund is computed, but there is no explicit when-to-use versus when-not guidance, no mention of prerequisites such as confirming booking status first, and no routing to alternatives.

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