Skip to main content
Glama

list_appointment_sms_confirmations

Read-onlyIdempotent

Read up to 50 recent SMS confirmation 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_confirmations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description does add two traits beyond that: a hard result cap of 50 and recency ordering. It says nothing about pagination, whether truncation is signalled, or what fields a record holds.

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 verb and resource, with the result cap and tenant scope attached inline. No filler and nothing an agent must read past to find the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description covers resource, scope, cap, and ordering, which is close to what an agent needs to call it. The residual gaps are the unstated id semantics and the absence of any truncation or paging note at the 50-record boundary.

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% and the single parameter 'id' has no description, so the schema gives an agent nothing. The description partially compensates by implying the id identifies an appointment ('for an appointment'), but it never names the parameter or states that it must be the appointment id rather than a contact or confirmation id.

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 uses a concrete verb ('Read') and a specific resource ('recent SMS confirmation records'), scoped to a single appointment and the approved business. It is clearly distinguishable from list_appointment_sms_reminders by the word 'confirmation', though it never explicitly contrasts the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of the near-identical reminders sibling, and no statement of prerequisites (e.g. whether the appointment must be confirmed or the business approved first). The only implied usage cue is 'for an appointment'.

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