Skip to main content
Glama
shadowfax92

MCP Apple Reminders

by shadowfax92

completeReminder

Mark reminders as completed in Apple Reminders by specifying the list name and reminder name to track tasks and maintain organized to-do lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNameYes
reminderNameYes

Implementation Reference

  • Core handler function that implements the logic to complete (mark as completed) a specific reminder in a given list by finding the list ID, locating the reminder by name, and updating its completed status to true.
    export async function completeReminder(listName: string, reminderName: string): Promise<boolean> {
      try {
        // First get the list ID by name
        const lists = await reminders.getLists();
        const targetList = lists.find(list => list.name === listName);
        
        if (!targetList) {
          throw new Error(`List "${listName}" not found`);
        }
        
        // Get all reminders from the list
        const reminderItems = await reminders.getReminders(
          targetList.id,
          ['name', 'id']
        );
        
        // Find the specific reminder by name
        const targetReminder = reminderItems.find(item => item.name === reminderName);
        
        if (!targetReminder) {
          return false; // Reminder not found
        }
        
        // Update the reminder to mark it as completed
        await reminders.updateReminder(targetReminder.id, {
          completed: true
        });
        
        return true;
      } catch (error) {
        console.error(`Failed to complete reminder "${reminderName}" in list "${listName}":`, error);
        throw new Error(`Failed to complete reminder: ${error}`);
      }
    }
  • src/index.ts:93-118 (registration)
    MCP tool registration for 'completeReminder', including input schema validation with Zod and wrapper handler that delegates to reminders.completeReminder and formats the response.
    server.tool(
      "completeReminder",
      { 
        listName: z.string(),
        reminderName: z.string()
      },
      async ({ listName, reminderName }) => {
        try {
          const success = await reminders.completeReminder(listName, reminderName);
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ success, message: success ? "Reminder marked as completed" : "Reminder not found" }) 
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ error: "Failed to complete reminder" }) 
            }],
            isError: true
          };
        }
      }
    );
  • Input schema definition using Zod for the completeReminder tool parameters: listName and reminderName as required strings.
    { 
      listName: z.string(),
      reminderName: z.string()
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shadowfax92/apple-reminders-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server