Skip to main content
Glama
aYon1997

Health Reminder MCP Server

by aYon1997

send_immediate_reminder

Send an immediate health reminder notification to prompt users to take breaks and move around, with customizable message, title, and sound settings.

Instructions

立即发送一次健康提醒通知(不影响定时器)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo提醒消息内容该起身活动一下了!
titleNo通知标题健康提醒
soundNo是否播放提示音

Implementation Reference

  • The switch case handler for the 'send_immediate_reminder' tool that constructs a notification config from input arguments, calls the sendNotification helper, and returns a formatted success response.
    case "send_immediate_reminder": {
      const config = {
        message: (args?.message as string) || "该起身活动一下了!",
        title: (args?.title as string) || "健康提醒",
        sound: args?.sound !== undefined ? (args.sound as boolean) : true,
        interval: 0, // 不使用
      };
    
      sendNotification(config);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              message: "已发送即时提醒通知",
            }, null, 2),
          },
        ],
      };
    }
  • Input schema defining the parameters for the send_immediate_reminder tool: optional message, title (strings), and sound (boolean).
    inputSchema: {
      type: "object",
      properties: {
        message: {
          type: "string",
          description: "提醒消息内容",
          default: "该起身活动一下了!",
        },
        title: {
          type: "string",
          description: "通知标题",
          default: "健康提醒",
        },
        sound: {
          type: "boolean",
          description: "是否播放提示音",
          default: true,
        },
      },
    },
  • Registration of the send_immediate_reminder tool in the tools array, including name, description, and input schema, used by ListToolsRequestHandler.
    {
      name: "send_immediate_reminder",
      description: "立即发送一次健康提醒通知(不影响定时器)",
      inputSchema: {
        type: "object",
        properties: {
          message: {
            type: "string",
            description: "提醒消息内容",
            default: "该起身活动一下了!",
          },
          title: {
            type: "string",
            description: "通知标题",
            default: "健康提醒",
          },
          sound: {
            type: "boolean",
            description: "是否播放提示音",
            default: true,
          },
        },
      },
    },
  • Core helper function that sends the system notification using node-notifier based on the config and logs the event. Directly called by the tool handler.
    function sendNotification(config: ReminderConfig) {
      notifier.notify({
        title: config.title,
        message: config.message,
        sound: config.sound,
        wait: false,
        timeout: 10,
      });
    
      console.log(`[${new Date().toLocaleString()}] 已发送提醒: ${config.message}`);
    }
  • Client-side convenience wrapper that calls the send_immediate_reminder MCP tool and handles the response display.
    async function sendImmediateReminder() {
      console.log("\n正在发送即时提醒...");
      const result = await callTool("send_immediate_reminder");
      if (result && result.success) {
        console.log("✓", result.message);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions the notification doesn't affect timers, which is useful behavioral context. However, it lacks critical details: whether this requires specific permissions, what happens if the system isn't running, whether notifications are guaranteed to deliver, or any rate limits. For a notification-sending tool with zero annotation coverage, 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 conveys the core purpose and key behavioral constraint ('不影响定时器'). Every word earns its place with zero waste, making it appropriately sized and front-loaded.

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 a notification-sending tool with 3 parameters, no annotations, and no output schema, the description provides basic purpose and one behavioral constraint. However, it lacks information about success/failure responses, error conditions, or system state requirements. It's minimally adequate but has clear gaps for a tool that performs an action with side effects.

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 three parameters (message, title, sound) with descriptions and defaults. The description adds no parameter-specific information beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('立即发送' - immediately send) and resource ('健康提醒通知' - health reminder notification), specifying it's a one-time notification that doesn't affect timers. It distinguishes from siblings like start_reminder/stop_reminder by emphasizing the immediate, non-recurring nature. However, it doesn't explicitly contrast with get_status.

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

Usage Guidelines3/5

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

The description implies usage context by stating '不影响定时器' (doesn't affect timers), suggesting this is for one-off reminders separate from scheduled ones. However, it doesn't provide explicit guidance on when to use this versus alternatives like start_reminder for recurring reminders or get_status for checking state.

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