DodoDentist Dental Clinic

Move a dental appointment

reschedule_appointment

DestructiveIdempotent

Use this when someone asks to move a patient's appointment to another day or time. Returns the moved appointment; its patient, providers, procedures and length stay the same and the patient's reminders move with it. Not for cancelling an appointment.

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>",
      "startTime": "<startTime>",
      "expectedLastEditTime": "<expectedLastEditTime>"
    },
    "name": "reschedule_appointment"
  }
}

Input Schema

Name	Required	Description
`startTime`	Yes	New start as an ISO 8601 time with the practice's UTC offset, such as 2026-11-20T15:30:00+01:00.
`appointmentId`	Yes	Id of the appointment, from list_appointments.
`durationMinutes`	No	New length in minutes. Leave it out to keep the current length.
`expectedLastEditTime`	Yes	The lastEditTime from list_appointments. An appointment changed since then is refused.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare non-read-only, destructive, idempotent and open-world behavior, so the description only needs to add context. It does: the moved appointment is returned, patient/providers/procedures/length are preserved, and reminders follow the new time — all non-obvious side effects. It does not mention the concurrency refusal behavior, though the schema covers that parameter.

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 compact sentences, front-loaded with the trigger, then outcome, then exclusion. Every clause carries information an agent would otherwise have to infer.

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?

An output schema exists and the input schema is fully documented, so return values and parameter formats need no prose. The description supplies the behavioral side effects an agent needs, though it omits any mention of what happens on a stale expectedLastEditTime beyond what the schema states.

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%, so all four parameters are already documented including the ISO 8601 format and the expectedLastEditTime optimistic-concurrency guard. The description adds little parameter-level meaning beyond noting that length stays the same, and that phrasing subtly undersells the optional durationMinutes parameter.

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?

The description pairs a specific verb ('move a patient's appointment to another day or time') with the resource and states what is preserved (patient, providers, procedures, length, reminders). It also explicitly separates the tool from cancel_appointment, so an agent can distinguish it from siblings without reading schemas.

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?

It gives a clear triggering condition ('when someone asks to move a patient's appointment') and an explicit exclusion ('Not for cancelling an appointment'). The only gap is that it does not name the alternative tool (cancel_appointment) for the exclusion, leaving the agent to infer the handoff.

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?