Skip to main content
Glama

Cancel a booking

cancel_booking
Destructive

Use this when the user wants to cancel a booked local home-service appointment. Pass the cancel_url from request_booking. This cancels the booking, sets status to canceled, and sends a cancellation email when the row changes. canceled is true only after the booking is canceled. A result with canceled false means the booking was not canceled; do not tell the user it was. An on-site visit stays visit_type on_site.

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

Input Schema

NameRequiredDescriptionDefault
tokenNoToken from the cancel_url query string. Required when cancel_url is omitted.
shop_idNoEnrolled shop id from search_businesses. Examples: florida-pole-barn, florida-security-concepts, booqer-demo-shop.
cancel_urlYesCancel link returned by request_booking, including the token. Example: https://booqer.ai/shops/florida-security-concepts/requests/11111111-1111-4111-8111-111111111111/cancel?token=example.
request_idNoBooking id returned by request_booking. UUID. Example: 11111111-1111-4111-8111-111111111111.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as destructive and open-world, and the description adds real behavioral detail the annotations lack: the booking status is set to canceled, a cancellation email is sent, and the `canceled` flag in the result must be checked before telling the user anything succeeded. The final sentence about visit_type staying on_site is unclear and adds little, which keeps this from a 5.

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?

The definition is short and front-loads the use case, then the critical false-result warning. The closing sentence about on-site visits and visit_type is cryptic and doesn't clearly earn its place, slightly diluting an otherwise tight description.

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 mutation with an output schema already present, the description covers the trigger, the required input source, the side effects, and how to interpret the result flag. It omits reversibility and any cancellation-window or permission constraints, which would matter for a destructive operation but are secondary here.

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%, so all four parameters are already documented, and the description's instruction to pass cancel_url from request_booking largely repeats the schema's own wording. It adds emphasis on which parameter matters but no new meaning about the token, shop_id, or request_id alternatives.

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 opens with a specific verb and resource: cancel a booked local home-service appointment. It ties itself to request_booking by name, so an agent can immediately tell it apart from the booking-creation and status-check siblings.

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?

It states the triggering condition clearly (the user wants to cancel a booked appointment) and directs the agent to pass cancel_url obtained from request_booking. It doesn't spell out explicit when-not cases, such as what to do if the booking ID is unknown or what to use instead of this tool for rescheduling.

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