himalaya-mcp

Overview Schema Source Related Servers Discussions Admin

create_reminder

Create a reminder in Apple Reminders for tasks and follow-ups from email. Set a title, optional notes, due date, and priority.

Instructions

Create a reminder in Apple Reminders (macOS only). Use for action items, follow-ups, and tasks extracted from email.

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

Name	Required	Description
`notes`	No	Optional notes or context for the reminder
`title`	Yes	Reminder title / task description
`dueDate`	No	Optional due date (ISO format, e.g. 2026-07-15T14:00:00)
`priority`	No	Priority 1-5 (1=highest)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Jul 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden. It only discloses the platform constraint 'macOS only' but does not mention any behavioral traits such as required permissions, side effects like notifications, or whether the Reminders app must be open. For a creation tool, this is insufficient.

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

Conciseness5/5

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

The description is two sentences with no wasted words. It front-loads the action and platform, then provides use cases. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, no output schema), the description covers purpose and basic context but lacks behavioral details. It doesn't mention return values or success indicators, which is a gap since there's no output schema. Additional context about integration with the Apple Reminders system would improve completeness.

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?

The input schema has 4 parameters with 100% description coverage, so the baseline is 3. The description does not add any additional meaning beyond what the schema already provides; it simply lists use cases without elaborating on parameter formats or defaults.

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

Purpose5/5

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

The description clearly states the verb 'Create', the resource 'reminder in Apple Reminders', and the platform constraint 'macOS only'. It also specifies use cases: action items, follow-ups, and tasks extracted from email, which distinguishes it from sibling tools like create_action_item or create_calendar_event.

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?

The description mentions 'Use for action items, follow-ups, and tasks extracted from email,' providing some context but does not explicitly state when not to use this tool or suggest alternatives (e.g., create_action_item for non-reminder tasks). No exclusions or competing tool references are given.

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