Skip to main content
Glama
snowild

Redmine MCP Server

by snowild

health_check

Verify the Redmine MCP Server's operational status to ensure it can manage projects, track issues, and perform searches effectively.

Instructions

健康檢查工具,確認服務器正常運作

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The health_check tool handler function. It checks the connection to the Redmine server using get_client() and test_connection(), returning a status message indicating if the server is healthy and connected.
    @mcp.tool()
    def health_check() -> str:
        """健康檢查工具,確認服務器正常運作"""
        try:
            config = get_config()
            client = get_client()
            # 測試連線
            if client.test_connection():
                return f"✓ 服務器正常運作,已連接到 {config.redmine_domain}"
            else:
                return f"✗ 無法連接到 Redmine 服務器: {config.redmine_domain}"
        except Exception as e:
            return f"✗ 服務器異常: {str(e)}"
  • The @mcp.tool() decorator registers the health_check function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions confirming server operation but doesn't disclose behavioral traits such as what the check entails (e.g., ping, status endpoints), whether it requires authentication, rate limits, or what happens on failure. The description is minimal and lacks operational 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 without unnecessary words. It's appropriately sized for a simple tool and front-loaded with the essential information. Every part of the description earns its place.

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

Completeness2/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 incomplete. It doesn't explain what 'normal operation' means, what the return value indicates (e.g., success/failure, status details), or how it integrates with sibling tools. For a health check tool, more context on behavior and output is needed despite the lack of structured fields.

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 no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'health check tool, confirm server normal operation', which is clear but vague. It specifies the verb ('confirm') and resource ('server operation'), but lacks detail on what constitutes 'normal operation' or how this differs from sibling tools like 'server_info'. It's not tautological with the name, but doesn't fully distinguish its scope.

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. With siblings like 'server_info' that might provide server status information, there's no indication of when this health check is preferred, what prerequisites exist, or any exclusions. Usage is implied only by the general purpose.

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/snowild/redmine-mcp'

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