Skip to main content
Glama

cancel_appointment

DestructiveIdempotent

Cancel a single appointment in the approved business using its current revision. Cancellation may refund a prepaid appointment.

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

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (destructive, idempotent, open-world), the description adds a genuine side effect an agent would not otherwise know: cancellation may refund a prepaid appointment. It also hints at an optimistic-concurrency requirement via 'current revision'. It does not say whether the cancellation is reversible, what permissions are required, or what happens when a stale revision is supplied.

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?

Two short sentences, the action and scope are front-loaded, and every clause carries information (scope, revision requirement, refund side effect). Nothing is redundant with the name.

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 mutation with no output schema and zero schema coverage on both parameters, the description covers the core action and a key side effect but omits error behavior on revision mismatch, permission requirements, and whether dependent records (payments, reminders) are affected.

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 0%, so the description must compensate and only partly does: 'using its current revision' explains that revision must be current, which is meaningful. The id parameter format (UUID, with a special all-zero/all-f case) and the failure behavior on a stale revision are left entirely to the schema.

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 names a specific verb (Cancel) and a specific resource (a single appointment), plus scope ('in the approved business'), which separates it from a bulk or class-session cancellation. It stops short of naming a sibling such as cancel_class_session explicitly, so the differentiation is inferred rather than stated.

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 only implied: an agent can infer this is the tool for cancelling one appointment. There is no stated when-not guidance, no mention of reschedule_appointment or cancel_class_session as alternatives, and no note about prerequisites such as obtaining the current revision first.

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