Veterical Vet Clinic

Move a vet appointment

reschedule_appointment

DestructiveIdempotent

Use this when someone asks to move an animal's appointment to another day or time. Returns the moved appointment; its animal, providers, procedures and length stay the same and the owner'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 clinic'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 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavior beyond that: the response returns the moved appointment, animal/providers/procedures/length are preserved, and the owner's reminders follow the move — a non-obvious side effect. It does not explain why the operation is flagged destructive or mention that stale edits are refused (the schema covers that).

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 tight sentences, front-loaded with the trigger before the return behavior and the exclusion. No redundant restatement of the title and no filler.

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, so return-shape detail is not required, and the description still captures the important invariant (fields and reminders carry over). The only gap is the optimistic-concurrency refusal path, which is documented only in the expectedLastEditTime schema field.

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?

With 100% schema description coverage, every parameter including durationMinutes' keep-current default is already documented in the schema. The phrase 'length stay the same' restates that default rather than adding new meaning. Baseline 3 is appropriate.

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 gives a specific verb and resource ('move an animal's appointment to another day or time') plus a scope constraint ('Not for cancelling an appointment'), which separates it from cancel_appointment and, by implication, book_appointment. An agent can pick this tool without opening any 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?

It states a concrete trigger ('when someone asks to move an animal's appointment') and one explicit exclusion (cancelling). What is missing is a positive pointer to the sibling that handles the excluded case, but the boundary is clear enough to route on.

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?