Skip to main content
Glama
Sign In
Apple Reminders MCP Server

Apple Reminders MCP Server

by leawn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

uncompleteReminder

Reopen a completed reminder in Apple Reminders by providing the list name and reminder ID.

Instructions

Mark a reminder as incomplete 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": "uncompleteReminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNameYesName of the reminder list
reminderIdYesID of the reminder to mark as incomplete

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?

With no annotations provided, the description bears the full burden of disclosing behavioral traits. It only states the action without mentioning side effects, permissions, or state changes beyond the basic purpose, leaving critical behavior undocumented.

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?

The description is a single, clear sentence with no unnecessary words. While it is concise, it could benefit from slightly more context about the tool's behavior without becoming verbose.

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?

Given the simplicity of the tool and the schema descriptions, the description provides the basic purpose. However, it lacks usage guidelines and behavioral transparency, which are needed for full contextual completeness.

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% (both parameters have descriptions in the schema), so the description adds no additional meaning beyond what the schema already provides. The baseline score is appropriate.

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 uses a specific verb ('Mark') and resource ('reminder') with a clear state change ('as incomplete'), which effectively distinguishes it from its sibling 'completeReminder' that performs the opposite action.

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 description implies use when an agent needs to revert a reminder's completion status, but it offers no explicit guidance on when to use this tool versus alternatives like 'completeReminder' or 'updateReminder'.

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