Skip to main content
Glama
shadowfax92

MCP Apple Reminders

by shadowfax92

createReminder

Add tasks to Apple Reminders with list name, title, due date, and notes. This tool helps users organize and track their to-dos through AI assistants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNameYes
titleYes
dueDateNo
notesNo

Implementation Reference

  • Handler function for the MCP 'createReminder' tool. It calls the helper function from reminders.ts, handles success/error responses in MCP format.
    async ({ listName, title, dueDate, notes }) => {
      try {
        const success = await reminders.createReminder(listName, title, dueDate, notes);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ success, message: success ? "Reminder created" : "Failed to create reminder" }) 
          }]
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ error: "Failed to create reminder" }) 
          }],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters: listName (required), title (required), dueDate (optional), notes (optional).
    { 
      listName: z.string(),
      title: z.string(),
      dueDate: z.string().optional(),
      notes: z.string().optional()
    },
  • src/index.ts:63-90 (registration)
    Registration of the 'createReminder' tool with the MCP server using server.tool(name, schema, handler).
    server.tool(
      "createReminder",
      { 
        listName: z.string(),
        title: z.string(),
        dueDate: z.string().optional(),
        notes: z.string().optional()
      },
      async ({ listName, title, dueDate, notes }) => {
        try {
          const success = await reminders.createReminder(listName, title, dueDate, notes);
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ success, message: success ? "Reminder created" : "Failed to create reminder" }) 
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ error: "Failed to create reminder" }) 
            }],
            isError: true
          };
        }
      }
    );
  • Core helper function implementing the reminder creation logic using the node-reminders library. Finds the target list, prepares data, creates the reminder, and returns success boolean.
    export async function createReminder(listName: string, title: string, dueDate?: string, notes?: 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`);
        }
        
        // Prepare reminder data
        const reminderData: any = {
          name: title
        };
        
        if (dueDate) {
          reminderData.dueDate = new Date(dueDate);
        }
        
        if (notes) {
          reminderData.body = notes;
        }
        
        // Create the reminder
        const newReminderId = await reminders.createReminder(targetList.id, reminderData);
        
        return !!newReminderId;
      } catch (error) {
        console.error(`Failed to create reminder "${title}" in list "${listName}":`, error);
        throw new Error(`Failed to create reminder: ${error}`);
      }
    }
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