Skip to main content
Glama

reminders_get_incomplete_reminders

Retrieve incomplete reminders from all lists on macOS to track pending tasks and manage follow-ups.

Instructions

Get incomplete reminders across all lists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of reminders to return (default: 10)

Implementation Reference

  • The handler function for 'reminders_get_incomplete_reminders' that runs an AppleScript command via osascript to fetch up to 'limit' (default 10) incomplete reminders from all Reminders lists, formats them with list names, and returns the result or error.
    case 'reminders_get_incomplete_reminders':
      try {
        const limit = (args?.limit as number) || 10;
        
        const command = `osascript -e 'on run argv
          set numLimit to (item 1 of argv) as number
          tell application "Reminders"
            set incompleteReminders to {}
            set reminderCount to 0
            repeat with aList in lists
              set listName to name of aList
              repeat with aReminder in reminders of aList
                if not completed of aReminder and reminderCount < numLimit then
                  set reminderName to name of aReminder
                  set reminderBody to body of aReminder
                  if reminderBody is missing value then set reminderBody to ""
                  set end of incompleteReminders to (reminderName & " (List: " & listName & ")")
                  set reminderCount to reminderCount + 1
                end if
              end repeat
            end repeat
            return incompleteReminders as string
          end tell
        end run' -- ${limit}`;
        
        const { stdout, stderr } = await execAsync(command);
        
        if (stderr.trim()) {
          return {
            content: [
              {
                type: 'text',
                text: `Error getting incomplete reminders: ${stderr.trim()}`,
              },
            ],
          };
        }
        
        const output = stdout.trim();
        if (!output || output === '') {
          return {
            content: [
              {
                type: 'text',
                text: 'No incomplete reminders found',
              },
            ],
          };
        }
        
        return {
          content: [
            {
              type: 'text',
              text: `Incomplete Reminders (limit: ${limit}):\n${output}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: `Error executing incomplete reminders command: ${error.message}`,
            },
          ],
        };
      }
  • src/index.ts:128-140 (registration)
    Tool registration in ListTools handler, including name, description, and input schema (optional 'limit' number).
    {
      name: 'reminders_get_incomplete_reminders',
      description: 'Get incomplete reminders across all lists',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of reminders to return (default: 10)',
          },
        },
      },
    },
  • Input schema definition for the tool: optional 'limit' parameter of type number.
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of reminders to return (default: 10)',
          },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the incomplete reminders come in. The description is minimal and lacks important behavioral context.

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 extremely concise - a single sentence that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it efficiently front-loaded.

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?

For a tool with no annotations, no output schema, and minimal description, this is inadequate. The description doesn't explain what 'incomplete reminders' means, what data is returned, or any behavioral constraints. Given the complexity of accessing reminder data across systems, more context is needed.

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 schema description coverage is 100% with one parameter ('limit') fully documented in the schema. The description doesn't add any parameter information beyond what's already in the schema, which is acceptable given the high schema coverage, resulting in the baseline score of 3.

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?

The description clearly states the verb ('Get') and resource ('incomplete reminders across all lists'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'reminders_get_lists' or 'reminders_create_reminder', which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use it over other reminder-related tools or when it's appropriate versus other methods of accessing reminders.

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/samicokar/mcp-mac'

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