Skip to main content
Glama

list_appointment_changes

Read-onlyIdempotent

List recorded changes for an appointment, newest first, with email status and times in Unix milliseconds. Supply changeId to look up a specific change. A sent status records provider acceptance. Check the customer inbox to verify receipt.

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>"
    },
    "name": "list_appointment_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
offsetNo
changeIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: results are ordered newest-first, timestamps are Unix milliseconds, and 'sent' means provider acceptance rather than customer receipt — a real semantic caveat. It stops short of describing pagination behavior or the shape of a change record.

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?

Four short sentences, front-loaded with the resource and ordering before the optional-mode hint and the status caveat. Nothing is padded; the only borderline item is the final inbox-verification remark, which earns its place as a caveat but is slightly conversational.

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?

With no output schema and zero parameter documentation, the description should do more: it never explains what a 'change' record contains, how pagination past the 50-item cap works, or what the returned email status values can be. It covers ordering and status semantics well but leaves structural gaps for a 4-parameter listing tool.

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 0%, so the description carries the burden, and it only partly does: it implicitizes 'id' as the appointment and explains changeId's role. The limit and offset parameters (including the hard max of 50) receive no explanation in either the schema or the description, leaving half the parameters opaque.

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?

The first sentence gives a specific verb and resource ('List recorded changes for an appointment') plus ordering ('newest first') and payload hints ('email status', 'Unix milliseconds'). It reads clearly as a per-appointment change-history lister, distinct from siblings like get_appointment or review_appointment_change_email, though it never names a sibling to sharpen the boundary.

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?

It does state a mode switch: 'Supply changeId to look up a specific change,' which tells the agent how to narrow to a single record. However, there is no guidance on when to use this versus related tools (e.g., the change-email review tool) and no prerequisite or exclusion statements.

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