Skip to main content
Glama
iCloud MCP Server Apple

iCloud MCP Server Apple

Update Reminder

update-reminder
DestructiveIdempotent

Update an existing reminder's title, notes, due date, or priority using its reminder ID. This works in LOCAL mode only.

Instructions

Updates an existing reminder (LOCAL mode only)

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": {
      "reminderId": "<reminderId>"
    },
    "name": "update-reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNew notes/description
nameNoNew title
dueDateNoNew due date in ISO format
priorityNoNew priority level
reminderIdYesID of the reminder to update (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose destructive, idempotent, non-read-only behavior, and the description adds only the local-mode scope. It does not explain what data is overwritten, whether omitted fields are preserved, or any auth requirements, leaving notable gaps even with annotations present.

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

Conciseness4/5

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

One front-loaded sentence with no redundant wording, and the scope constraint is placed immediately after the purpose. It is efficient, though the terse parenthetical is slightly under-explained rather than maximally clear.

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?

For a destructive partial-update tool, the definition omits critical update semantics: whether only supplied fields change, whether omitted fields are preserved, and what local mode excludes. The schema and annotations cover fields and safety flags, but the description does not complete the picture an agent needs.

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 description coverage is 100%, so all five parameters, including the required reminderId, are documented in the schema. The description adds no parameter meaning beyond what the schema provides, which meets the baseline but no more.

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 the verb 'Updates' and resource 'existing reminder', and adds the scope constraint 'LOCAL mode only'. It is clear, though it does not explicitly contrast with complete-reminder or update-event, so it is not maximally differentiated.

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?

The parenthetical 'LOCAL mode only' signals a precondition, implying use when updating a local reminder. However, it does not say when to use complete-reminder or delete-reminder instead, or what to do outside local mode, so guidance is only implied.

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