Local MCP

Create Reminder

create_reminder

Destructive

Creates a reminder in Reminders.app. To make it repeat pass recurrence (daily/weekly/monthly/yearly) with a due_date. A due_date with a date but no time sets the due date without an alarm, so Reminders will not notify; include a time to get a notification.

Input Schema

Name	Required	Description
`notes`	No	Notes (optional)
`title`	Yes	Reminder title
`confirm`	No	Ignored; kept for older clients.
`due_date`	No	ISO 8601 date (optional)
`priority`	No	Priority: none \| low \| medium \| high (optional)
`list_name`	No	Reminder list name (optional)
`recurrence`	No	Make it a repeating reminder: 'daily', 'weekly', 'monthly', or 'yearly' (optional; omit or 'none' for a one-time reminder). A repeating reminder needs a due date.
`recurrence_count`	No	Total number of occurrences (optional). Mutually exclusive with recurrence_until; if neither is given it repeats indefinitely. Needs recurrence.
`recurrence_until`	No	ISO 8601 date the repetition stops on (optional; takes precedence over recurrence_count). Needs recurrence.
`recurrence_interval`	No	Repeat every N periods (optional, default 1 — e.g. recurrence='weekly' + recurrence_interval=2 = every 2 weeks). Needs recurrence.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026
- changedInput schema / properties / confirm / description
```
Previous value: -"Must be true to create"New value: +"Ignored; kept for older clients."
```

Changed4 schema fields changedOct 22, 2026

addedInput schema / properties / recurrence

Added value: +{
+  "description": "Make it a repeating reminder: 'daily', 'weekly', 'monthly', or 'yearly' (optional; omit or 'none' for a one-time reminder). A repeating reminder needs a due date.",
+  "enum": [
+    "daily",
+    "weekly",
+    "monthly",
+    "yearly",
+    "none"
+  ],
+  "type": "string"
+}

addedInput schema / properties / recurrence_count

Added value: +{
+  "description": "Total number of occurrences (optional). Mutually exclusive with recurrence_until; if neither is given it repeats indefinitely. Needs recurrence.",
+  "type": "integer"
+}

addedInput schema / properties / recurrence_interval

Added value: +{
+  "description": "Repeat every N periods (optional, default 1 — e.g. recurrence='weekly' + recurrence_interval=2 = every 2 weeks). Needs recurrence.",
+  "type": "integer"
+}

addedInput schema / properties / recurrence_until

Added value: +{
+  "description": "ISO 8601 date the repetition stops on (optional; takes precedence over recurrence_count). Needs recurrence.",
+  "type": "string"
+}

First observedJun 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare it is not read-only and is destructive, so the mutation profile is already carried; the description adds a non-obvious behavioral trait — a date-only due_date silently produces no alarm/notification. It omits permission/authorization requirements (Reminders.app access) and what happens when list_name is omitted.

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?

Three short sentences, front-loaded with the core action, then the two most failure-prone parameter interactions. No filler, though the delivery could be tightened into a bullet-like structure.

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?

With 10 parameters, full schema coverage, an output schema, and annotations present, the description covers the risky interactions an agent would otherwise get wrong. It leaves minor gaps around default-list behavior and the recurrece_count/until precedence, but those are documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns extra by explaining the cross-parameter dependency between `recurrence` and `due_date`, and the time-vs-no-time semantics of `due_date` that the schema does not spell out.

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?

States a specific verb and resource ('Creates a reminder in Reminders.app'), which is unambiguous against siblings like update_reminder or create_reminder_list. It does not explicitly contrast itself with alternative creation tools (todoist_create_task, create_omnifocus_task), but the target app makes intent clear.

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?

Gives operational guidance on when to pass `recurrence` and when a `due_date` will or won't notify, which is genuinely useful. However, it offers no guidance on when to choose this tool over sibling creation tools or when not to use it.

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.