Skip to main content
Glama

Cancel an appointment

cancel_appointment

Cancel a salon appointment by appointment ID and reason. Cancellation fees may apply per salon policy.

Instructions

Cancel an existing appointment by appointmentId (from list_my_appointments). Cancellation fees may apply per the salon's policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonYesReason for cancellation
appointmentIdYes
Behavior3/5

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

No annotations provided, so description must disclose behaviors. It warns about cancellation fees but does not mention other side effects (e.g., refunds, reversibility, notifications). Adequate but minimal.

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?

Single sentence, no wasted words. Front-loaded with main action.

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?

No output schema; description does not explain return values or confirmation behavior. Lacks information on success/error handling. Adequate for simple tool but incomplete.

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?

Adds context to appointmentId by linking it to list_my_appointments. Reason parameter is already described in schema; description does not add further value. Overall, useful beyond schema for one of two parameters.

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?

Clearly states action (cancel), object (appointment), and method (by appointmentId from list_my_appointments). Distinct from sibling tools like book_appointment or find_availability.

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?

Implies when to use: after obtaining appointmentId from list_my_appointments. Mentions cancellation fees as a consideration but does not explicitly state when not to use.

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/topness-msft/salonrunner-mcp'

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