Skip to main content
Glama

cancel_appointment

Destructive

Cancel an appointment. Sets status cancelled, removes the Google Calendar and GoHighLevel events of a booking made in ChatGenius (an event imported from the owner's own calendar is left alone), fires appointment.cancelled. 409 already_cancelled if it already is. Send {} as the body.

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": {
      "id": "<id>"
    },
    "name": "cancel_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing exactly what is changed, which external events are removed, that imported calendar events are not touched, the emitted event, and the 409 already_cancelled failure mode. This is strong behavioral context for a destructive mutation.

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?

The description is front-loaded and dense with useful facts: status change, event removal scope, side effect, and error condition. Every sentence contributes to correct invocation or expectation setting.

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?

For a one-parameter destructive tool with no output schema, this covers the essential behavior: what is mutated, what is preserved, what side effect fires, and how an already-cancelled case behaves. No critical invocation context appears missing.

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 100%, so the required integer id is already documented. The description does not add meaning to the id parameter itself, and the 'Send {} as the body' instruction is invocation detail rather than parameter semantics.

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?

States a specific verb and resource ('Cancel an appointment') and immediately clarifies the concrete effects: status change, calendar/GHL event removal, and event emission. It is distinguishable from sibling tools like reschedule_appointment or update_appointment.

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?

The action context is clear, and the description notes an important scoping rule that imported events are left alone. It does not explicitly contrast with reschedule_appointment or update_appointment, but the cancellation use case is unambiguous.

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