Skip to main content
Glama

create_reminder

Creates a reminder with a title and optional due date, list, notes, URL, or priority so users can capture tasks and schedule follow-ups in Apple Reminders.

Instructions

Create a reminder. The due date is ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00. A date-only 'due' has a day but no time. Subtasks and tags are not supported, because EventKit has no public API for them.

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": {
      "title": "<title>"
    },
    "name": "create_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoDue date. ISO 8601, for example 2026-11-12 or 2026-11-12T09:30:00+01:00
urlNoA URL, for example https://example.com.
listNoList name or id. Default: the default list.
notesNoNotes.
titleYesReminder title.
priorityNoPriority. Default none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already cover the safety profile (non-read-only, non-destructive, closed-world), so the description's job is to add context, which it does by explaining the EventKit limitation that blocks subtasks and tags. It does not say what is returned on success (e.g., a reminder id) or what happens on invalid input or duplicate titles, leaving the post-call situation unclear.

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, with no filler. The only waste is restating the ISO 8601 example verbatim from the schema, which does not add information for the agent.

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?

For a 6-parameter creation tool with full schema coverage and annotations, the description covers the trickiest input (date-only versus datetime) and preempts two unsupported features. Missing is any statement of the creation result — a reminder identifier or confirmation — which matters for chaining into update_reminder or complete_reminder.

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%, so the baseline is 3, and the description largely repeats the schema's ISO 8601 example for the 'due' parameter. It does add one genuinely useful semantic, clarifying that a date-only 'due' has a day but no time, but the other five parameters (title, list, notes, url, priority) get no description-level clarification.

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 opens with a specific verb and resource ("Create a reminder"), which is unambiguous. However, it does not distinguish this tool from siblings such as create_reminder_list or update_reminder, so the agent must rely on the name alone to pick the right tool for reminder creation.

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?

Usage is implied rather than stated: the agent can infer this is the tool for making a new reminder, and the note that subtasks and tags are unsupported tells it what will not work. There is no explicit guidance on when to use this versus update_reminder or how to handle an existing reminder, which is the main gap.

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