Local MCP

List Reminders

list_reminders

Read-only

Lists reminders from Apple Reminders (Reminders.app) on this Mac. Optionally filter by completion status or list name. For Microsoft To Do use todo_list_tasks instead.

Input Schema

Name	Required	Description
`limit`	No	Max number of reminders to return (earliest due first). Optional; defaults to all.
`offset`	No	Skip this many reminders first. A long answer is cut at 256 KB with truncated=true and next_offset: pass next_offset here to continue.
`completed`	No	false or omitted = incomplete (the default). true = completed. There is no 'both': ask twice if you need them.
`list_name`	No	Filter by reminder list name (optional)
`completed_since`	No	With completed=true: only reminders completed on or after this ISO 8601 date or datetime (optional). Applied before limit.
`completed_until`	No	With completed=true: only reminders completed on or before this ISO 8601 date or datetime (optional). Inclusive when only a date is given: 2026-10-02 includes the whole of October 2. Applied before limit.

Output Schema

Name	Required	Description
`count`	No	Number returned in this response.
`total`	No	Total matching before the limit.
`reminders`	No
`truncated`	No	True when the answer was cut at 256 KB: see next_offset.
`next_offset`	No	Pass as offset to get the next reminders (present only when the answer was cut).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026

addedInput schema / properties / completed_since

Added value: +{
+  "description": "With completed=true: only reminders completed on or after this ISO 8601 date or datetime (optional). Applied before limit.",
+  "type": "string"
+}

addedInput schema / properties / completed_until

Added value: +{
+  "description": "With completed=true: only reminders completed on or before this ISO 8601 date or datetime (optional). Inclusive when only a date is given: 2026-10-02 includes the whole of October 2. Applied before limit.",
+  "type": "string"
+}

addedOutput schema / properties / reminders / items / properties / recurrence

Added value: +{
+  "description": "Present only when the reminder repeats: daily | weekly | monthly | yearly. With recurrence_interval (when above 1), recurrence_count and recurrence_until (a date) when the repetition has them.",
+  "type": "string"
+}

Changed3 schema fields changedOct 10, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many reminders first. A long answer is cut at 256 KB with truncated=true and next_offset: pass next_offset here to continue.",
+  "type": "integer"
+}

addedOutput schema / properties / next_offset

Added value: +{
+  "description": "Pass as offset to get the next reminders (present only when the answer was cut).",
+  "type": "integer"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the answer was cut at 256 KB: see next_offset.",
+  "type": "boolean"
+}

Changed1 schema field changedAug 30, 2026

changedInput schema / properties / completed / description

Previous value: -"true=completed, false=incomplete (default), omit=all"New value: +"false or omitted = incomplete (the default). true = completed. There is no 'both': ask twice if you need them."

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context that this reads from the local Apple Reminders app and is not the Microsoft To Do integration, though it does not itself describe pagination or truncation behavior because the schema and output schema cover those.

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?

Two focused sentences with no wasted language; the primary source and scope are front-loaded before the alternative-tool note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given read-only annotations, a complete input schema, and an output schema, the description provides enough context to select and invoke the tool correctly. It identifies the data source and the relevant alternative without needing to duplicate structured metadata.

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%, and the parameter descriptions already document limit, offset, completion status, and completed date ranges in detail. The description only restates that filtering by completion status or list name is optional, so baseline 3 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?

States a specific verb and resource ("Lists reminders"), identifies the exact source (Apple Reminders on this Mac), and explicitly distinguishes it from the Microsoft To Do sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage boundary by naming the alternative tool for Microsoft To Do tasks (todo_list_tasks) and summarizes the optional filtering modes available for this tool.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.