Skip to main content
Glama

review_appointment_change_email

Read-onlyIdempotent

Read the saved recipient and latest appointment change before asking the owner to approve the email. Pass a proposed message to review it with the booking details. Times are Unix milliseconds.

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": "review_appointment_change_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world scope, so safety is covered. The description adds value beyond that by saying it reads stored recipient and appointment-change data plus booking details and is meant to precede owner approval, confirming this is a non-mutating preview step. It still does not say whether a review is persisted or what a rejection path looks like.

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 precondition, then the action, then the unit convention. Nothing is padded, though the Unix-milliseconds sentence dangles without saying which fields it applies to.

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?

There is no output schema, so the description must describe what comes back; it only gestures at "the saved recipient" and "booking details" without naming the review verdict or fields. Combined with an undocumented required `id`, an agent has enough to attempt the call but not to predict or interpret the result confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters, so the description must carry the burden. It clarifies `message` as an optional proposed body to be reviewed, but says nothing about the required `id` UUID — an agent cannot tell from the text whether that identifies the appointment, the change, or the recipient — and the 3000-character cap is unmentioned. The trailing "Times are Unix milliseconds" note describes return values, not parameters.

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 pairs specific verbs with specific resources: "Read the saved recipient and latest appointment change" and "review [a proposed message] with the booking details." The review/preview intent is clear enough to separate it from the mutating sibling send_appointment_change_email, but that sibling is never named, so the distinguishing boundary is left to inference.

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?

"before asking the owner to approve the email" places the tool at a specific point in the approval workflow, which is real when-to-use guidance. However, there is no explicit when-not, no statement that it never sends anything, and the natural alternative (send_appointment_change_email) is never mentioned.

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