Skip to main content
Glama

Update reminder

update_reminder
Destructive

Update a reminder's title, note, schedule, or channels.

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": {
      "reminder_id": "<reminder_id>"
    },
    "name": "update_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
titleNo
remind_onNo
notify_smsNo
start_dateNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
remind_timeNoLocal reminder time in HH:MM format.
reminder_idYes
notify_emailNo
schedule_kindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description never explains what makes this destructive: whether unspecified fields are cleared, whether schedule edits overwrite existing occurrences, or how a once-to-daily change behaves. For a mutation tool flagged as destructive, saying nothing about overwrite/reversibility is a real gap.

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

Conciseness3/5

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

One clean, front-loaded sentence with no filler, so structurally sound. However, its size is mismatched to a 10-parameter destructive mutation, making it terseness rather than genuine economy.

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

Completeness2/5

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

No output schema exists and there are 10 parameters at 20% description coverage, with a destructive annotation to justify. The description supplies almost none of the semantic detail an agent would need to call this safely, so it is materially incomplete for the tool's complexity.

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 coverage is only 20% across 10 parameters, so the description carries the burden and does not meet it. It names title and note (already self-evident from the schema) and gestures at 'schedule' and 'channels', but adds nothing about reminder_id placement, business_id's single-business default, remind_time format, or how schedule_kind interacts with remind_on/start_date.

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 and resource ('Update a reminder') plus the affected fields (title, note, schedule, channels), which lets an agent separate it from create_reminder, delete_reminder, and complete_reminder by resource alone. It stops short of explicitly naming the sibling condition (e.g. 'to mark done, use complete_reminder'), so it lands at clear-but-not-differentiating.

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 prerequisites, and no exclusion such as 'use complete_reminder instead to mark a reminder finished'. The agent must infer usage purely from the verb.

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