Skip to main content
Glama
aYon1997

Health Reminder MCP Server

by aYon1997

start_reminder

Schedule periodic system notifications to remind users to take breaks and move around, with customizable intervals, messages, and notification settings.

Instructions

启动健康提醒定时器,每隔指定时间弹出系统通知

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intervalNo提醒间隔时间(分钟),默认 30 分钟
messageNo提醒消息内容该起身活动一下了!久坐对健康不利,建议站起来走动走动。
titleNo通知标题健康提醒
soundNo是否播放提示音

Implementation Reference

  • Core handler function that starts the reminder: clears existing timer, sends immediate notification using node-notifier, sets up recurring setInterval timer.
    function startReminder(config: ReminderConfig) {
      // 清除现有定时器
      if (reminderTimer) {
        clearInterval(reminderTimer);
      }
    
      currentConfig = { ...config };
      const intervalMs = config.interval * 60 * 1000;
    
      // 立即发送一次通知
      sendNotification(config);
    
      // 设置定时器
      reminderTimer = setInterval(() => {
        sendNotification(config);
      }, intervalMs);
    
      console.log(`✓ 健康提醒已启动 - 每 ${config.interval} 分钟提醒一次`);
    }
  • JSON Schema for input validation of start_reminder tool parameters: interval, message, title, sound.
    inputSchema: {
      type: "object",
      properties: {
        interval: {
          type: "number",
          description: "提醒间隔时间(分钟),默认 30 分钟",
          default: 30,
        },
        message: {
          type: "string",
          description: "提醒消息内容",
          default: "该起身活动一下了!久坐对健康不利,建议站起来走动走动。",
        },
        title: {
          type: "string",
          description: "通知标题",
          default: "健康提醒",
        },
        sound: {
          type: "boolean",
          description: "是否播放提示音",
          default: true,
        },
      },
    },
  • Tool registration object defining name, description, and schema, included in the tools list returned by listTools.
    {
      name: "start_reminder",
      description: "启动健康提醒定时器,每隔指定时间弹出系统通知",
      inputSchema: {
        type: "object",
        properties: {
          interval: {
            type: "number",
            description: "提醒间隔时间(分钟),默认 30 分钟",
            default: 30,
          },
          message: {
            type: "string",
            description: "提醒消息内容",
            default: "该起身活动一下了!久坐对健康不利,建议站起来走动走动。",
          },
          title: {
            type: "string",
            description: "通知标题",
            default: "健康提醒",
          },
          sound: {
            type: "boolean",
            description: "是否播放提示音",
            default: true,
          },
        },
      },
    },
  • MCP CallToolRequestSchema handler case for start_reminder: constructs config from arguments, invokes startReminder, formats MCP response.
    case "start_reminder": {
      const config: ReminderConfig = {
        interval: (args?.interval as number) || defaultConfig.interval,
        message: (args?.message as string) || defaultConfig.message,
        title: (args?.title as string) || defaultConfig.title,
        sound: args?.sound !== undefined ? (args.sound as boolean) : defaultConfig.sound,
      };
    
      startReminder(config);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              message: `健康提醒已启动!每 ${config.interval} 分钟将收到提醒通知。`,
              config: config,
            }, null, 2),
          },
        ],
      };
    }
  • TypeScript interface defining the shape of ReminderConfig used in handler signatures.
    interface ReminderConfig {
      interval: number; // 提醒间隔(分钟)
      message: string; // 提醒消息
      title: string; // 通知标题
      sound: boolean; // 是否播放声音
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states basic behavior (starts timer, pops system notifications). It doesn't disclose important traits like whether this requires system permissions, if it runs in background, error handling, or how it interacts with existing reminders. For a tool with potential system-level impact, this is insufficient.

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 a single, efficient Chinese sentence that directly states the tool's core functionality with zero wasted words. It's appropriately sized and front-loaded with the essential action.

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?

For a timer-starting tool with 4 parameters and no output schema, the description covers the basic purpose but lacks important context about system requirements, persistence, and error behavior. Without annotations, it should provide more operational details for a tool that interacts with system notifications.

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?

Schema description coverage is 100%, so the schema already documents all 4 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score.

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

Purpose5/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 with specific verb ('启动' - start) and resource ('健康提醒定时器' - health reminder timer), and distinguishes it from siblings by specifying it creates a recurring timer (vs. send_immediate_reminder for one-time or stop_reminder for stopping).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (to start recurring reminders with system notifications) but doesn't explicitly contrast with alternatives like send_immediate_reminder or mention prerequisites. However, the context is clear enough for basic differentiation.

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/aYon1997/health-reminder-mcp'

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