Skip to main content
Glama

reschedule_appointment

Change an appointment's start and end using its current revision. Times are Unix milliseconds. Review the customer notification in Cockatoo.

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": {
      "id": "<id>",
      "revision": "<revision>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "reschedule_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
endYes
startYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

It adds some behavior beyond the annotations: updates are keyed to the current revision, and a customer notification is involved. It doesn't say what happens when the revision is stale (an error, presumably) or whether the notification is sent automatically. The reference to 'Cockatoo' is an unexplained, ambiguous referent, so the agent cannot act on it.

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?

Three short sentences with the action front-loaded. The final sentence ('Review the customer notification in Cockatoo') is vague and adds noise, but no other wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation with no output schema, the essentials (units, revision semantics) are present, but gaps remain: no mention of error behavior on revision conflict, permission needs, or what the response contains. The notification reference is too unclear to fill a gap.

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?

Schema coverage is 0%, so the description has to carry the parameter meanings, and it covers the two non-obvious ones: time fields are Unix milliseconds, and the revision is the current revision of the appointment, an optimistic-concurrency token. The id parameter is not described, but it's clear from the resource context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: change an appointment's start and end. It clearly does not schedule, cancel, or complete an appointment, which separates it from the cancel/complete/create siblings, though it does not name a sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the revision requirement hints that this is for rescheduling an existing appointment, but the description doesn't say when to prefer it over cancel+create or what prerequisites are needed. No exclusions or alternatives are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources