cancel_appointment
Destructive
Cancel an existing appointment. Requires full scope.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Cancellation reason | |
| appointmentId | Yes | The appointment ID |
lacita
TDQS
A3.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose destructive/non-read-only behavior; description adds the 'full scope' authorization requirement, which is useful beyond structured fields. It does not contradict annotations.
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 concise sentences with essential info front-loaded; no filler.
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 simple two-param cancellation tool, description plus annotations and schema sufficiently cover purpose, required auth, and destructive nature. No output schema, but return values are not critical here; minor gap in not mentioning post-cancellation effects.
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 covers both parameters with descriptions (100% coverage), so description needn't elaborate. 'Requires full scope' is not parameter-specific; reason and appointmentId are adequately defined in 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?
Description uses specific verb 'Cancel' and resource 'existing appointment', clearly indicating the action. It doesn't explicitly distinguish from sibling 'reschedule_appointment', but purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to prefer cancellation over alternatives like reschedule_appointment, nor any exclusions. 'Requires full scope' is a prerequisite, not usage guidance.
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.
TDQS
A3.5/5.0
Disambiguation3/5
Most tools are clearly distinct, but update_calendar overlaps with specialized tools like update_booking_settings, update_confirmation_settings, and the reminder management tools (add/delete/get reminders). This creates ambiguity about which tool to use for modifying specific settings such as buffers or reminders, though descriptions help clarify the intended scope.
Naming Consistency5/5
All 28 tools follow a consistent verb_noun snake_case pattern (e.g., create_calendar, get_appointments, update_contact). The verbs are predictable (add, cancel, create, delete, get, reschedule, send, update), making the API easy to navigate.
Tool Count2/5
With 28 tools, the set exceeds the 25+ threshold typically considered too many. While each tool serves a legitimate purpose, the high number is overwhelming and likely includes more granularity than necessary; some settings tools could be consolidated.
Completeness5/5
The tool surface covers the full lifecycle of calendars, appointments, and contacts, including availability, overrides, reminders, confirmation settings, and notifications. There are no obvious dead ends or missing operations; cancellation and rescheduling handle appointment changes, and send_invitation covers creation.