Skip to main content
Glama

list_appointment_sms_reminders

Read-onlyIdempotent

Read up to 50 recent SMS reminder 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_sms_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 readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful context beyond them — a 50-record cap, recency ordering, and business-level scoping — but never says whether the cap means silent truncation, how to get older records, or what a record contains. With annotations carrying the safety burden, that residual gap keeps it at 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and capped result size, with no filler or redundancy. Nothing in it needs to be trimmed.

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?

This is a simple single-parameter read tool whose annotations already cover safety, so the description is close to sufficient. The remaining holes — truncation at 50, pagination, and return-field shape with no output schema — leave an agent guessing about what comes back.

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 must carry the load, and it does reasonably: "for an appointment" tells the agent that the lone `id` parameter is an appointment identifier rather than a business, contact, or reminder ID. It does not state the accepted ID format, but the core semantics of the single required parameter are conveyed.

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 gives a specific verb (read/list) and resource (SMS reminder records) scoped to one appointment, and the word "SMS" implicitly separates it from the email-reminder and SMS-confirmation siblings. It stops short of naming an alternative outright, so the differentiation is inferential rather than explicit.

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: query this when you need an appointment's recent SMS reminders. There is no explicit when-not guidance, no statement about how it relates to list_appointment_sms_confirmations or get_appointment_reminder_settings, and no prerequisites beyond the vague "approved business" phrase.

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