Skip to main content
Glama
Sign In
Apple Reminders MCP Server

Apple Reminders MCP Server

by Krishna-Desiraju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_completed_reminders

Retrieve completed Apple Reminders within a specified date range to track task completion and review past activities.

Instructions

Get completed reminders within a date range

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_completed_reminders"
  }
}

Input Schema

NameRequiredDescriptionDefault
startDateNoStart date in ISO 8601 format (optional)
endDateNoEnd date in ISO 8601 format (optional)

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action is to 'Get' (implying a read operation) but doesn't cover aspects like pagination, rate limits, authentication needs, or what happens if date parameters are omitted. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool's low complexity (2 optional parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic action and scope but lacks details on usage guidelines, behavioral traits, and output format, which are important for an agent to use it effectively without annotations.

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?

The schema description coverage is 100%, with both parameters ('startDate' and 'endDate') documented as optional ISO 8601 dates. The description adds context by implying date-range filtering but doesn't provide additional semantics beyond what the schema already states, such as default behaviors or format details. This meets the baseline for high schema coverage.

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?

The description clearly states the verb 'Get' and resource 'completed reminders' with the scope 'within a date range', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_reminders' or 'get_overdue_reminders' beyond the 'completed' qualifier, which is why it doesn't achieve a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_reminders' (which might include all reminders) or 'get_overdue_reminders'. There's no mention of prerequisites, exclusions, or contextual usage, leaving the agent to infer based on tool names alone.

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