Skip to main content
Glama
MikeyBeez

MCP Reminders

by MikeyBeez

help

Access guidance for setting and managing reminders within Claude's note-taking system to track tasks across sessions.

Instructions

Get help on using reminders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'help' tool. Returns the predefined HELP_DOCUMENTATION as a text content block in the tool response.
    case 'help': {
      return {
        content: [{ type: 'text', text: HELP_DOCUMENTATION }],
      };
    }
  • src/index.ts:323-330 (registration)
    Registration of the 'help' tool in the list of tools returned by ListToolsRequestHandler, including name, description, and empty input schema.
    {
      name: 'help',
      description: 'Get help on using reminders',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Helper constant containing the full documentation text returned by the 'help' tool.
    const HELP_DOCUMENTATION = `
    # MCP Reminders Server
    
    A simple reminder system for Claude - like "Alexa, remind me..." but for AI.
    Leave notes for yourself across sessions, check them when you start, act on them or save them.
    
    ## Available Functions:
    
    ### remind_me(reminder, priority?)
    Add a reminder to the queue.
    - reminder: What to remember
    - priority: "high", "normal", "low" (default: "normal")
    Returns: Reminder ID
    
    ### check_reminders(filter?)
    Check your reminders.
    - filter: Optional - "all", "high", "normal", "low" (default: "all")
    Returns: List of reminders sorted by priority and time
    
    ### complete_reminder(id)
    Mark a reminder as completed/handled.
    - id: Reminder ID
    Returns: Confirmation
    
    ### delete_reminder(id)
    Delete a reminder without completing it.
    - id: Reminder ID
    Returns: Confirmation
    
    ### move_to_notes(id, note?)
    Move a reminder to permanent notes (Obsidian).
    - id: Reminder ID
    - note: Optional additional note
    Returns: Confirmation
    
    ### clear_old_reminders(days?)
    Clear reminders older than N days.
    - days: Number of days (default: 7)
    Returns: Number cleared
    
    ### help()
    Show this documentation.
    
    ## Usage Pattern:
    1. Start session: check_reminders()
    2. See what needs attention
    3. Work on items, then complete_reminder(id)
    4. Important items: move_to_notes(id)
    5. Clean up: clear_old_reminders()
    
    ## Examples:
    - remind_me("Test the new contemplation loop integration", "high")
    - remind_me("Look into why AppleScript restart lost context")
    - check_reminders("high")
    - complete_reminder("rem_12345")
    `;
Behavior2/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. 'Get help' implies a read-only, informational operation, but the description doesn't specify what kind of help is returned (text documentation, examples, interactive guidance), whether authentication is required, or if there are any rate limits. For a tool with zero annotation coverage, this represents significant behavioral gaps.

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 perfectly concise at just four words: 'Get help on using reminders.' Every word earns its place - 'Get' (verb), 'help' (action), 'on using' (scope), 'reminders' (domain). There's zero redundancy or unnecessary elaboration, making it immediately understandable.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally complete. It identifies the tool's purpose but lacks details about what the help contains, how it's formatted, or when it's most useful. For a help tool that presumably returns informational content, more guidance about the nature and format of the returned help would be beneficial.

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

Parameters4/5

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

The tool has zero parameters with 100% schema description coverage, so the baseline score is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents this. No additional parameter semantics are needed or provided.

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 tool's purpose as 'Get help on using reminders' - a specific verb ('Get help') with a clear resource domain ('using reminders'). It distinguishes itself from sibling tools that perform actions on reminders (check, clear, complete, delete, move, create) by focusing on assistance rather than direct manipulation. However, it doesn't specify what form the help takes (documentation, examples, troubleshooting).

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 indicate whether this should be used before attempting other reminder operations, when users are confused about syntax, or as a general reference. With six sibling tools performing various reminder operations, the lack of usage context leaves the agent guessing about appropriate invocation scenarios.

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