Skip to main content
Glama

send_appointment_change_email

Idempotent

Email the latest appointment change to its saved customer. Confirm the recipient and message with the owner before sending. Supply the change ID, revision and recipient from the reviewed 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": {
      "id": "<id>",
      "changeId": "<changeId>",
      "recipient": "<recipient>",
      "revision": "<revision>"
    },
    "name": "send_appointment_change_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
messageNo
changeIdYes
revisionYes
recipientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true (external side effect), idempotentHint=true, and non-read-only, so the safety profile is partially covered. The description adds genuinely non-structured context: an owner confirmation gate before sending and the requirement to use values from the reviewed appointment. It does not describe what happens on failure, whether the sent email is recorded, or how revision guards against stale sends.

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, front-loaded with the action and then the safety gate. The final sentence partially restates the parameter sourcing already implied, which is mild redundancy but still useful since the schema has no descriptions.

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 an externally visible mutation with no output schema and zero schema documentation, the description is only adequate. It covers the confirmation workflow but omits return behavior, error handling, and whether the email is irreversible or logged.

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 coverage is 0%, so the description carries the full burden and only partly discharges it. It explains changeId, revision, and recipient as values taken from the reviewed appointment, but says nothing about `id` (presumably the appointment) or the optional `message` parameter, leaving two of five parameters without meaning.

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 description states a specific verb and resource -- emailing an appointment change notification to the customer -- and scopes it to the latest change. It distinguishes itself implicitly from the review sibling by requiring input 'from the reviewed appointment', though it never names that 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 Guidelines4/5

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

"Confirm the recipient and message with the owner before sending" gives a concrete precondition for invoking the tool, and "from the reviewed appointment" implies review must happen first. It stops short of naming the review tool as the required preceding step or stating when not to send.

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