complete_reminder

Mark reminders as complete in macOS using AI agents. Check off tasks through Claude, Cursor, or Windsurf directly in your native Reminders app without manual input.

Instructions

Mark a reminder as complete

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:82-86 (registration)
Registration of complete_reminder tool (along with all other tools) in a loop. Each tool is registered with an empty schema and a stub handler that returns a static message indicating this is an inspection stub.
```
for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}
```
server.js:28-28 (schema)
Definition of complete_reminder in the TOOLS array with its description "Mark a reminder as complete". This is used for tool discovery/registration.
```
["complete_reminder", "Mark a reminder as complete"],
```

Tool Definition Quality

B3.1/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. While 'Mark...as complete' implies state mutation, it fails to disclose if this is reversible, if the reminder is archived or deleted, side effects, or authentication requirements.

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?

Extremely efficient at 5 words with zero redundancy. The single sentence front-loads the core action immediately.

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?

Critically incomplete given the empty parameter schema. Fails to explain how the tool identifies which specific reminder to complete (likely requires external context or implicit state not documented here). No output schema or annotations to compensate.

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

Parameters4/5

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

Input schema contains zero parameters. Per calibration rules, 0 params warrants a baseline score of 4. The description does not need to compensate for missing parameter documentation.

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 action (Mark...as complete) on a clear resource (reminder). Implicitly distinguishes from sibling 'complete_omnifocus_task' by specifying 'reminder' versus 'task', though it doesn't clarify they belong to different apps/systems.

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?

Provides no guidance on when to use this versus 'complete_omnifocus_task', nor prerequisites (e.g., does it require a specific reminder to be 'selected' or context from a prior tool call?). No alternative workflows mentioned.

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

Install Server

Pilot MCP