Skip to main content
Glama

create_reminder

Adds a reminder to a specified Apple Reminders list, with optional due date and notes, so users can capture tasks directly from MCP clients.

Instructions

Create a reminder in an Apple Reminders list.

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
dueNoISO 8601 due date, e.g. 2026-12-01T09:00:00+07:00
listNoReminders list nameReminders
notesNo
titleYesReminder title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses almost nothing: not whether the list must pre-exist or is auto-created, not what happens on duplicate titles, not what identifier or result comes back, and not that this is a mutating write. Only the fact that it targets Apple Reminders is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero padding, so there is nothing to trim. However, the brevity reflects under-specification rather than disciplined economy, since key operational details were never included.

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?

For a four-parameter mutation tool with no annotations and no output schema, this description leaves too much unspecified: creation side effects, default-list behavior, and result shape are all absent. It is not sufficient for an agent to call the tool confidently in edge cases.

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

Parameters2/5

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

Schema coverage is 75%, leaving notes undocumented, and the description adds no parameter meaning beyond the schema — it does not clarify the ISO 8601 due format, whether list defaults to "Reminders", or which fields are optional. It only vaguely gestures at the list concept through the phrase "in an Apple Reminders list".

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?

"Create a reminder in an Apple Reminders list" gives a specific verb (create), a specific resource (reminder), and the target system (Apple Reminders). It is unambiguous on its own, but it never distinguishes itself from the sibling list_reminders or explains how the two relate.

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?

There is no when-to-use guidance at all: no mention of when to create versus list or search reminders, no prerequisites such as the target list needing to exist or account access being required. An agent must infer all routing decisions from the tool name alone.

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