Fresha MCP Server and API by Cotlet

Cancel appointment

cancel_appointment

Destructive

Cancel an appointment without a charge, optionally telling the client. Cancels the appointment as Cancel in its drawer does, with one of the business's cancellation reasons. With notify_client (default true) Fresha sends the client a cancellation message, so this can reach the client; false cancels quietly. whole_series also cancels the later appointments of a repeating series. An appointment with a cancellation fee or a paid deposit is refused: cancel it in Fresha. It cannot be undone here. By default you confirm each call; you can switch that off for this tool. Waits for the owner's approval.

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

Input Schema

Name	Required	Description
`scope`	No	this_appointment (default) or whole_series, for repeating appointments: this and every later one.
`reason`	No	Name of one of the business's cancellation reasons, e.g. Client not available. Default: none.
`notify_client`	No	Send the client a cancellation message. Default: true.
`appointment_id`	Yes	Appointment id from list_appointments.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Far exceeds the annotations (destructiveHint, openWorldHint, idempotentHint=false). It discloses the outward-facing side effect of notify_client reaching the client, the refusal condition for fee/deposit appointments, irreversibility ('It cannot be undone here'), the confirmation prompt and the owner approval gate.

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?

Effect and safety-critical constraints (no charge, refusal, irreversible) lead, which is the right ordering for a destructive tool. Slightly dense run-on sentences and the near-duplicate confirmation/owner-approval lines cost it a point.

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?

With no output schema, the description covers the main outcomes an agent must anticipate: quiet vs notified cancellation, series expansion, and hard refusal. It stops short of saying what a successful call returns, but the safety-critical picture is complete.

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?

Coverage is 100%, so the schema already documents all four parameters; the description still earns credit by adding consequence-level meaning to notify_client ('this can reach the client') and whole_series ('also cancels the later appointments'), rather than just restating the schema.

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?

A specific verb (cancel) plus resource (appointment), with the key distinguishing scope condition (no charge) stated up front. The analogy 'as Cancel in its drawer does' anchors it to a concrete UI behavior, and the naturally opposing sibling reschedule_appointment is clearly not what this does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions and an alternative path: appointments with a cancellation fee or paid deposit are refused and must be cancelled 'in Fresha'. Also routes whole_series usage for repeating appointments, so an agent knows both when to call and when not to.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fresha MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.