Skip to main content
Glama
Sign In
icloud-mcp

icloud-mcp

by adamzaidi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_reminder

Add a new reminder to an iCloud Reminders list with title and optional due date, notes, or priority. Use it to capture tasks and deadlines.

Instructions

Create a new reminder in iCloud Reminders.

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

Input Schema

NameRequiredDescriptionDefault
dueNoDue date/time — ISO 8601 (e.g. 2026-03-20T09:00:00)
notesNoNotes / description
titleYesReminder title
listNameYesList name to add the reminder to (required)
priorityNoPriority: high, medium, low, or none (default none)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

C2.9/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 behavioral burden. It does not disclose whether the target list must pre-exist, what happens to duplicate titles, whether defaults are applied, or what is returned; 'Create' implies mutation with no further detail.

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?

A single, front-loaded sentence with no filler or redundancy. It is appropriately terse for the resource, though the brevity borders on under-specification rather than earned conciseness.

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 mutation tool with no annotations and no output schema, the description is too thin: it omits prerequisites, return behavior (e.g., a reminder ID needed for complete_reminder), and any interaction with list state. The agent lacks enough to invoke it confidently.

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%, with each parameter documented (title, listName, due, notes, priority) in the schema itself. The description adds no extra param meaning, so the baseline of 3 applies.

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 (Create) and resource (reminder in iCloud Reminders), clearly distinct from create_reminder_list and update_reminder. However, it does not explicitly differentiate itself from its close siblings, so it stops short of a 5.

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 gives no when-to-use guidance, no prerequisites (e.g., must the list already exist?), and no mention of alternatives like create_reminder_list or update_reminder. The agent must infer context entirely.

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