Skip to main content
Glama
aYon1997

Health Reminder MCP Server

by aYon1997

stop_reminder

Stop the periodic health reminder notifications from the Health Reminder MCP Server to pause break prompts.

Instructions

停止健康提醒定时器

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'stop_reminder' tool. It clears the active reminder timer interval if it exists, logs a stop message, and returns true if stopped or false otherwise.
    function stopReminder() {
      if (reminderTimer) {
        clearInterval(reminderTimer);
        reminderTimer = null;
        console.log("✓ 健康提醒已停止");
        return true;
      }
      return false;
    }
  • Registers the 'stop_reminder' tool in the list of available tools, specifying its name, description, and input schema (empty object). This is used for the ListTools response.
    {
      name: "stop_reminder",
      description: "停止健康提醒定时器",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The dispatch handler in the CallToolRequestSchema that invokes the stopReminder function and formats the response.
    case "stop_reminder": {
      const stopped = stopReminder();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: stopped,
              message: stopped ? "健康提醒已停止" : "当前没有运行中的提醒",
            }, null, 2),
          },
        ],
      };
    }
  • The input schema definition for the 'stop_reminder' tool, which requires no parameters (empty properties).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • Global state variables used by the stopReminder handler: the timer reference that gets cleared and current config.
    let reminderTimer: NodeJS.Timeout | null = null;
    let currentConfig: ReminderConfig = { ...defaultConfig };
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. It states the action ('stop') but doesn't describe what happens when invoked (e.g., whether it's idempotent, if it returns confirmation, if it affects scheduled reminders, or if it requires specific permissions). This leaves significant gaps for a mutation tool.

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 sentence in Chinese that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity (a mutation with no parameters) and lack of annotations/output schema, the description is minimally adequate but incomplete. It states what the tool does but omits behavioral details (e.g., effects, return values, error conditions) that would help an agent use it correctly in context with siblings.

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 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it doesn't incorrectly imply parameters exist. A baseline of 4 is appropriate for zero-parameter tools.

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 ('停止' meaning 'stop') and the target resource ('健康提醒定时器' meaning 'health reminder timer'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'start_reminder' or 'send_immediate_reminder' beyond the obvious semantic difference.

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 like 'start_reminder' or 'send_immediate_reminder', nor does it mention prerequisites (e.g., whether a reminder must be running first) or exclusions. Usage is implied from the name but not explicitly stated.

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