Skip to main content
Glama
Sign In
Apple Reminders MCP Server

Apple Reminders MCP Server

by leawn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

completeReminder

Complete a reminder in Apple Reminders by specifying the list name and reminder ID.

Instructions

Mark a reminder as completed in Apple Reminders

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": {
      "listName": "<listName>",
      "reminderId": "<reminderId>"
    },
    "name": "completeReminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNameYesName of the reminder list
reminderIdYesID of the reminder to complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states the basic action without detailing side effects (e.g., irreversibility, state changes, or permission requirements).

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?

The description is a single, clear sentence that conveys the tool's purpose without superfluous information. It is well-structured and front-loaded.

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 simple mutation tool with 2 well-defined required parameters and no output schema, the description is adequate. It could mention the return value or success indication, but given the simplicity, it is nearly complete.

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%, and the description adds no extra meaning beyond the parameter descriptions. Both listName and reminderId are already explained in the input schema, so the description provides no added value for parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the action 'mark as completed' and the resource 'reminder in Apple Reminders'. Among sibling tools like createReminder, deleteReminder, and uncompleteReminder, it clearly distinguishes its role.

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?

No guidance on when to use this tool versus alternatives, such as uncompleteReminder or updateReminder. No prerequisites or contextual cues are provided, leaving the agent to infer usage.

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

Deploy Server

Other Tools