Skip to main content
Glama
shadowfax92

MCP Apple Reminders

by shadowfax92

getReminders

Retrieve reminders from a specific Apple Reminders list to help users view and manage their tasks through AI assistants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNameYes

Implementation Reference

  • The handler function for the 'getReminders' MCP tool. It takes a listName parameter, fetches reminders using the helper, handles errors, and returns JSON-formatted reminders in MCP response format.
    async ({ listName }) => {
      try {
        const items = await reminders.getRemindersFromList(listName);
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ reminders: items }) 
          }]
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ error: `Failed to get reminders from list: ${listName}` }) 
          }],
          isError: true
        };
      }
    }
  • Input schema for the getReminders tool using Zod, requiring a 'listName' string parameter.
    { listName: z.string() },
  • src/index.ts:38-59 (registration)
    Registration of the 'getReminders' tool on the MCP server, specifying name, input schema, and handler function.
    server.tool(
      "getReminders",
      { listName: z.string() },
      async ({ listName }) => {
        try {
          const items = await reminders.getRemindersFromList(listName);
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ reminders: items }) 
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({ error: `Failed to get reminders from list: ${listName}` }) 
            }],
            isError: true
          };
        }
      }
  • Supporting helper function that retrieves reminders from a specific list: finds list by name, calls node-reminders.getReminders, formats the output.
    export async function getRemindersFromList(listName: string): Promise<any[]> {
      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 reminders from the list with specific properties
        const reminderItems = await reminders.getReminders(
          targetList.id,
          ['name', 'completed', 'dueDate', 'priority', 'body']
        );
        
        // Format the reminders to match the expected output format
        return reminderItems.map(item => ({
          name: item.name,
          completed: item.completed || false,
          dueDate: formatDate(item.dueDate),
          priority: item.priority || 0,
          notes: item.body
        }));
      } catch (error) {
        console.error(`Failed to get reminders from list "${listName}":`, error);
        throw new Error(`Failed to get reminders from list "${listName}": ${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