Skip to main content
Glama

update_appointment_reminder_settings

Idempotent

Set email and SMS appointment reminder preferences and lead time in minutes. Enabling reminders requires Pro.

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": {
      "enabled": "<enabled>",
      "leadMinutes": "<leadMinutes>",
      "sms": "<sms>"
    },
    "name": "update_appointment_reminder_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
smsYes
enabledYes
whatsappNo
leadMinutesYes
leadMinutes2No
leadMinutes3No
importantInfoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / importantInfo
      Added value: +{
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • addedInput schema / properties / leadMinutes2
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "const": 60,
      +          "type": "number"
      +        },
      +        {
      +          "const": 120,
      +          "type": "number"
      +        },
      +        {
      +          "const": 1440,
      +          "type": "number"
      +        },
      +        {
      +          "const": 2880,
      +          "type": "number"
      +        },
      +        {
      +          "const": 10080,
      +          "type": "number"
      +        }
      +      ]
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / leadMinutes3
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "const": 60,
      +          "type": "number"
      +        },
      +        {
      +          "const": 120,
      +          "type": "number"
      +        },
      +        {
      +          "const": 1440,
      +          "type": "number"
      +        },
      +        {
      +          "const": 2880,
      +          "type": "number"
      +        },
      +        {
      +          "const": 10080,
      +          "type": "number"
      +        }
      +      ]
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / whatsapp
      Added value: +{
      +  "type": "boolean"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare it non-read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the Pro-plan prerequisite for enabling reminders, which is behavioral context not present in any structured field. It stops short of saying what happens to unmentioned fields (whatsapp, leadMinutes2/3) or what is returned.

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?

Two sentences, no filler, with the capability stated first and the gating prerequisite second. Every clause carries information the agent needs.

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 7-parameter mutation tool with zero schema coverage and no output schema, the description is too thin: the multi-tier lead-time fields, the whatsapp channel and the importantInfo note are all invisible to the agent. The Pro prerequisite partially offsets this, but an agent could easily call it with wrong field semantics.

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% across 7 parameters, so the description carries the full burden and largely does not. It explains 'lead time in minutes' but omits the only five permitted values (60, 120, 1440, 2880, 10080), leaves whatsapp, leadMinutes2, leadMinutes3 and importantInfo (max 1000 chars) entirely unexplained, and mentions 'email' even though no email parameter exists in the schema.

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?

States a specific verb ('Set') plus the resource ('appointment reminder preferences') and names the channels (email, SMS) and the lead-time unit. It is distinguishable from the read-side sibling get_appointment_reminder_settings by verb alone, though the description never names that counterpart explicitly.

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 only implied by the verb 'Set'; there is no explicit when-to-use or when-not-to-use guidance relative to get_appointment_reminder_settings or the other reminder-settings siblings. The one real guideline given is the prerequisite 'Enabling reminders requires Pro', which is genuinely useful but is a gate, not a routing rule.

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