DodoDentist Dental Clinic

Cancel a dental appointment

cancel_appointment

DestructiveIdempotent

Use this when someone asks to cancel a patient's appointment. Returns the appointment as canceled, kept rather than deleted, and whether the practice's cancellation message goes to the patient. 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 8, 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, idempotentHint=true, and readOnlyHint=false, but the description adds genuinely new behavior: the appointment is kept rather than deleted (soft cancel) and the practice's cancellation message may go to the patient. This refines what 'destructive' actually means here, which annotations alone could not convey. It does not cover rate limits or permission requirements, but those are not implied to be unusual.

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 short sentences, front-loaded with the trigger condition, then the behavioral outcome, then the exclusion. No filler and nothing buried.

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 annotations covering safety/idempotency, an output schema covering return values, and full schema coverage on both parameters, the description only needs purpose, effect, and boundary — all of which it supplies in three sentences.

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 both parameters (appointmentId, expectedLastEditTime) document their provenance from list_appointments and the staleness refusal. The description adds nothing about parameters, so the baseline 3 applies — the schema carries this dimension entirely.

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 a patient's appointment) and immediately scopes it against the nearest sibling by stating it is 'Not for moving an appointment to another time.' An agent can distinguish cancel from reschedule without opening either schema.

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 an explicit trigger ('when someone asks to cancel a patient's appointment') plus a clear negative exclusion for rescheduling. It stops short of naming reschedule_appointment directly, leaving the agent to infer the alternative tool name from the sibling list.

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

All DodoDentist Dental 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?