Skip to main content
Glama
aYon1997

Health Reminder MCP Server

by aYon1997

get_status

Check current health reminder settings and status to monitor break intervals and notification configurations for maintaining regular movement.

Instructions

获取当前健康提醒的状态和配置

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_status' tool within the CallToolRequestSchema handler. It calls getReminderStatus() and returns a JSON-formatted response with the current reminder status.
    case "get_status": {
      const status = getReminderStatus();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              status: status.active ? "运行中" : "已停止",
              active: status.active,
              config: status.config,
            }, null, 2),
          },
        ],
      };
    }
  • Helper function that provides the current status of the health reminder timer (whether active and current configuration).
    function getReminderStatus() {
      return {
        active: reminderTimer !== null,
        config: currentConfig,
      };
    }
  • Registration of the 'get_status' tool in the tools array, returned by ListToolsRequestSchema handler. Includes name, description, and empty input schema.
    {
      name: "get_status",
      description: "获取当前健康提醒的状态和配置",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for 'get_status' tool: empty object (no parameters required).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • Client-side wrapper function getStatus() that calls the 'get_status' tool and prints the result in a user-friendly format.
    async function getStatus() {
      console.log("\n正在获取状态信息...");
      const result = await callTool("get_status");
      if (result && result.success) {
        console.log("\n=== 当前状态 ===");
        console.log(`状态: ${result.status}`);
        if (result.active) {
          console.log("\n当前配置:");
          console.log(`  - 间隔时间: ${result.config.interval} 分钟`);
          console.log(`  - 标题: ${result.config.title}`);
          console.log(`  - 消息: ${result.config.message}`);
          console.log(`  - 提示音: ${result.config.sound ? "开启" : "关闭"}`);
        }
      }
    }
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. The description only states what the tool does ('get current health reminder status and configuration') without revealing any behavioral traits such as whether it's read-only (implied but not stated), what permissions might be required, whether it returns real-time or cached data, error conditions, or response format. For a tool with zero annotation coverage, this is a significant gap in behavioral context.

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 with zero wasted words. It's appropriately sized for a simple, parameterless tool and is front-loaded with the core functionality. Every word earns its place by conveying essential information about what the tool retrieves.

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 annotations, no output schema), the description is minimally adequate. It tells the agent what the tool does but lacks details on behavioral aspects (e.g., read-only nature, response format) that would be helpful. For a status retrieval tool with no structured metadata, the description should ideally provide more context about what 'status and configuration' includes or how the data is returned, but it meets the bare minimum for such a simple tool.

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, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to compensate for any parameter documentation gaps. It appropriately doesn't mention parameters, as none exist. The baseline for 0 parameters is 4, as there's no parameter information to add beyond what the schema provides.

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: '获取当前健康提醒的状态和配置' translates to 'Get current health reminder status and configuration'. This specifies the verb ('get') and resource ('health reminder status and configuration'), making it clear what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'send_immediate_reminder' or 'start_reminder', which appear to be action-oriented tools rather than status retrieval tools.

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. While the purpose implies it's for retrieving status/configuration (unlike siblings that perform actions like sending or starting reminders), there's no explicit mention of when this tool is appropriate, what prerequisites might exist, or when to choose other tools. The agent must infer usage from the tool name and description alone.

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