Skip to main content
Glama

cancel_booking

DestructiveIdempotent

Cancel a hotel reservation by providing guest first name, last name, and confirmation number. Always confirm with the guest before proceeding to avoid accidental loss of non-refundable rates.

Instructions

Cancel a hotel reservation. Cannot be undone.

REQUIRED — must collect ALL before calling:

  1. Guest first name AND last name

  2. Hotel confirmation number

Always confirm with the guest before proceeding. Remind them if the rate was non-refundable — canceling means they lose the full amount.

To change dates: search for new dates first, book the new reservation, THEN cancel the old one. Never cancel first — they could lose the room.

Cancellation confirmation is emailed to the address on file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameYesGuest first name on the reservation
last_nameYesGuest last name on the reservation
confirmation_numberYesHotel confirmation number
Behavior5/5

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

Adds behavioral details beyond annotations: 'Cannot be undone', email confirmation, guest confirmation requirement, non-refundable reminder. Annotations already indicate destructiveHint=true, and description aligns.

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?

Concise yet comprehensive. Front-loaded with purpose, followed by clear list of required inputs, then conditional procedures. No unnecessary words.

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?

Explains cancellation outcome (email), prerequisites, safety considerations, and change-date workflow. Fully covers the tool's scope given no output schema.

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 covers all three parameters with descriptions. Description reinforces collection requirements and adds operational context (must collect all before calling, confirm with guest). Adds value beyond schema.

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 clearly states the tool cancels a hotel reservation and is irreversible. It distinguishes itself from siblings like book_hotel, get_booking, etc., by specifying its destructive action.

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

Usage Guidelines5/5

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

Provides explicit instructions on when to use (cancelling), confirms with guest, and warns against cancelling before booking new dates. Offers an alternative procedure for date changes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/STAYKER-COM/1Stay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server