Skip to main content
Glama

update_reminder

Idempotent

Modify fields of an existing reminder by sending only the values to change, such as due date, notes, URL, list, title, or priority. Use an empty string to clear due, notes, or URL.

Instructions

Change fields of a reminder. Send only the fields to change. An empty string clears 'due', 'notes' or 'url'. 'list' moves the reminder to another list. The due date is ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00.

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": "update_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReminder id from list_reminders, search_reminders or get_reminder.
dueNoNew due date. Empty string clears it. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
urlNoNew URL. Empty string clears it.
listNoMove the reminder to this list (name or id). Names ignore case.
notesNoNew notes. Empty string clears them.
titleNoNew title.
priorityNoPriority. Default none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive and idempotent, and the description adds the important behavioral detail that an empty string clears 'due', 'notes' or 'url', plus that 'list' relocates the reminder. That is genuine value beyond the structured fields, though it leaves open what happens on failure or what the call returns.

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?

Four short sentences, front-loaded with the patch contract and followed by the two gotchas (empty-string clearing, list relocation) and the format example. Nothing is redundant or buried.

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 7-parameter partial-update tool with full schema coverage and explicit annotations, the definition covers the risky cases. It is slightly incomplete in not saying whether empty string also clears 'title' or resets 'priority', and in not indicating what the call returns since no output schema exists.

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 100%, so the schema already documents every parameter including the priority enum and the id source. The description's ISO 8601 example and clearing semantics largely restate the per-parameter schema text, so it adds only modest meaning beyond it.

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?

'Change fields of a reminder' gives a specific verb and resource, and the patch-style framing distinguishes it from create_reminder and delete_reminder. It does not explicitly name a sibling to route away from (e.g. complete_reminder for marking done), so it falls short of a 5.

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?

'Send only the fields to change' is clear how-to-invoke guidance and the clearing rule is stated. However, there is no when-to-use-this-vs-alternatives guidance, in particular no pointer that completing a reminder should go through complete_reminder rather than setting fields here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.