Veterical Vet Clinic

Cancel a vet appointment

cancel_appointment

DestructiveIdempotent

Use this when someone asks to cancel an animal's appointment or decline one an owner requested. Returns the appointment as canceled, kept rather than deleted, and whether the clinic's cancellation message goes to the owner. Not for moving an appointment to another time.

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

Input Schema

Name	Required	Description	Default
`appointmentId`	Yes	Id of the appointment, from list_appointments.
`expectedLastEditTime`	Yes	The lastEditTime from list_appointments. An appointment changed since then is refused.

Output Schema

Name	Required	Description	Default
`status`	Yes
`appointment`	Yes
`clientNotification`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description usefully reframes that: the appointment is 'kept rather than deleted,' so an agent knows the destructive flag means state change, not data loss. It also discloses that the result reports whether the clinic's cancellation message reaches the owner, which is non-obvious behavior not present in 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?

Three sentences, each earning its place: trigger condition first, then mutation semantics and return signal, then the exclusion. No boilerplate or redundancy.

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?

With an output schema present, return detail need not be spelled out, yet the description still flags the two most decision-relevant outcomes. For a two-parameter mutation tool with full schema coverage and rich annotations, nothing an agent needs in order to call it correctly is 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 description coverage is 100%, and the schema already explains both appointmentId's source and the optimistic-concurrency role of expectedLastEditTime. The description adds no additional parameter guidance, so the baseline of 3 applies.

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?

Names a specific verb and resource ('cancel an animal's appointment') and covers the secondary case ('decline one an owner requested'). It also explicitly rules out the adjacent operation ('Not for moving an appointment to another time'), which separates it cleanly from reschedule_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?

Gives a clear triggering condition (owner asks to cancel or decline a requested appointment) and a clear exclusion (rescheduling), which implies the correct alternative among siblings. It stops short of naming reschedule_appointment directly or stating prerequisites such as needing a fresh lastEditTime before attempting the call.

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

All Veterical Vet Clinic 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.

Resources

Need Help?