nucleus-apple-mcp

Overview Schema Source Related Servers Discussions Admin

reminders.create_reminder

Create a reminder with title, optional notes, URL, and priority. Set start and due dates to manage tasks across your lists.

Instructions

Create a reminder.

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

Input Schema

Name	Required	Description
`list_id`	Yes	List identifier.
`title`	Yes	Reminder title.
`start`	No	Start date/time (ISO-8601 datetime or YYYY-MM-DD).
`due`	No	Due date/time (ISO-8601 datetime or YYYY-MM-DD).
`notes`	No	Reminder notes.
`url`	No	Reminder url.
`priority`	No	Priority (0-9; 0 means none).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0May 29, 2026

TDQS

C2.2/5.0

Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as side effects, authentication needs, or what happens on creation beyond the basic action.

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

Conciseness2/5

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

Extremely brief (1 sentence) but too under-specified to be useful; conciseness should not sacrifice informativeness.

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?

Despite good schema coverage and an output schema (per context), the description lacks any context about return values, side effects, or interaction with other tools, making it incomplete.

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 coverage is 100% with descriptions for all 7 parameters, so the description adds no additional meaning; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Create a reminder' is a tautology that restates the tool name without adding specificity or distinguishing it from sibling tools like 'reminders.update_reminder'.

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?

No guidance on when to use this tool versus alternatives (e.g., notes.create_note, reminders.update_reminder), nor any prerequisites or context provided.

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