Skip to main content
Glama
Sign In
Apple Reminders MCP Server

Apple Reminders MCP Server

by leawn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

getReminders

Retrieve reminders from a specified Apple Reminders list. Optionally include completed reminders to review past tasks.

Instructions

Get reminders from a specific list 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>"
    },
    "name": "getReminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNameYesName of the reminder list to get reminders from
includeCompletedNoWhether to include completed reminders (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden but does not disclose behavioral traits like read-only nature, default behavior of includeCompleted, or return format (e.g., array of reminder objects). The agent cannot infer side effects or performance implications.

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?

Single sentence, efficient and front-loaded. No wasted words. Could be expanded slightly to add value without sacrificing conciseness.

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 provided, and the description does not explain the return structure (e.g., fields of each reminder, pagination). The description is incomplete for an agent to anticipate the tool's output and use it effectively.

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% with parameter descriptions, so baseline is 3. The description adds minimal extra meaning beyond the schema (e.g., tying 'specific list' to listName). No additional semantics like validation rules or default handling.

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 clearly states the action ('Get reminders'), the resource ('from a specific list'), and the context ('Apple Reminders'). It distinguishes from sibling tools like createReminder and deleteReminder by being a read operation.

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 like listReminderLists (which lists all lists) or updateReminder. No context on prerequisites or scenarios where this tool is appropriate.

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