Skip to main content
Glama
MikeyBeez

MCP Reminders

by MikeyBeez

check_reminders

Retrieve and view your scheduled reminders, with options to filter by priority level for organized task management.

Instructions

Check your reminders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter by priority (default: all)

Implementation Reference

  • Handler for the check_reminders tool. Retrieves reminders using the filter, formats them by priority and creation time, and returns a formatted text response.
    case 'check_reminders': {
      const { filter } = args as { filter?: string };
      const items = reminders.getReminders(filter);
      
      if (items.length === 0) {
        return {
          content: [{ type: 'text', text: 'No active reminders.' }],
        };
      }
      
      const formatted = items.map(r => 
        `[${r.priority.toUpperCase()}] ${r.id}: ${r.content}\n  Created: ${r.created}`
      ).join('\n\n');
      
      return {
        content: [{ type: 'text', text: `Active reminders:\n\n${formatted}` }],
      };
    }
  • Input schema definition for the check_reminders tool, specifying optional filter parameter.
    name: 'check_reminders',
    description: 'Check your reminders',
    inputSchema: {
      type: 'object',
      properties: {
        filter: {
          type: 'string',
          enum: ['all', 'high', 'normal', 'low'],
          description: 'Filter by priority (default: all)'
        }
      },
    },
  • src/index.ts:250-263 (registration)
    Registration of the check_reminders tool in the list of available tools.
    {
      name: 'check_reminders',
      description: 'Check your reminders',
      inputSchema: {
        type: 'object',
        properties: {
          filter: {
            type: 'string',
            enum: ['all', 'high', 'normal', 'low'],
            description: 'Filter by priority (default: all)'
          }
        },
      },
    },
  • Helper method in ReminderManager that fetches active reminders, applies filter if provided, sorts by priority then age, and returns the list.
    getReminders(filter: string = 'all'): Reminder[] {
      let reminders = Array.from(this.reminders.values())
        .filter(r => r.status === 'active');
      
      if (filter !== 'all') {
        reminders = reminders.filter(r => r.priority === filter);
      }
      
      // Sort by priority (high first) then by creation time (oldest first)
      const priorityOrder = { high: 0, normal: 1, low: 2 };
      reminders.sort((a, b) => {
        const priDiff = priorityOrder[a.priority] - priorityOrder[b.priority];
        if (priDiff !== 0) return priDiff;
        return new Date(a.created).getTime() - new Date(b.created).getTime();
      });
      
      return reminders;
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Check your reminders' implies a read operation but doesn't specify whether it's safe (non-destructive), what permissions are needed, how results are returned (list format, pagination), or any rate limits. It fails to describe key behavioral traits beyond the basic action.

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 with just three words, making it front-loaded and efficient. There's no wasted verbiage or redundancy, though this brevity contributes to gaps in other dimensions. Every word earns its place by conveying the core action and scope.

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?

Given the tool's moderate complexity (a read operation with filtering) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'check' entails (e.g., returns a list of reminders with details), how results are structured, or behavioral aspects like safety. For a tool with no output schema, more detail on return values would be helpful.

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 input schema has 100% description coverage, with the single parameter 'filter' clearly documented in the schema (enum values and default). The description adds no parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting. However, it doesn't compensate for any gaps since there are none.

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

Purpose2/5

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

The description 'Check your reminders' is a tautology that essentially restates the tool name 'check_reminders'. It doesn't specify what 'check' means operationally (list, view, verify status) or what resource scope is involved (all reminders, active ones, etc.). While it mentions 'your reminders' indicating personal scope, it lacks the specificity needed to distinguish it from siblings like 'clear_old_reminders' or 'complete_reminder'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when this tool is appropriate (e.g., to review pending reminders) versus when to use siblings like 'complete_reminder' (to mark one as done) or 'clear_old_reminders' (to remove outdated ones). There's no context about prerequisites, timing, or exclusions.

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/MikeyBeez/mcp-reminders'

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