Skip to main content
Glama

list_appointment_email_reminders

Read-onlyIdempotent

Read up to 50 recent email reminder delivery records for an appointment in the approved business.

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_email_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds the useful 'up to 50 recent' volume bound, but leaves 'recent' undefined (no time window) and says nothing about ordering or truncation behavior when more than 50 records exist.

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?

One front-loaded sentence with no wasted clauses; the scope and the cap arrive before the qualifier. The trailing phrase 'in the approved business' is slightly opaque jargon but does convey tenant scoping.

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 simple one-parameter read tool with no output schema, the description covers subject, scope and volume limit. It is still missing the meaning of 'recent', the record ordering, and any sense of what fields a delivery record contains, which an agent would need to interpret results.

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% for the single `id` parameter, so the schema gives no hint about what the identifier refers to. The description partially compensates by saying the records are 'for an appointment', implying `id` is an appointment identifier, but it never states this unambiguously or gives a format.

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?

States a specific verb (read), a specific resource (email reminder delivery records), and constrains scope to one appointment and a 50-record cap. The word 'email' cleanly separates it from the sibling list_appointment_sms_reminders without needing to name it.

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 by 'for an appointment', so an agent can infer it is the per-appointment reminder-history lookup. There is no explicit when-not condition, no mention of the SMS sibling, and no guidance on when to prefer a settings or reminder-configuration tool instead.

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