Skip to main content
Glama
mcp-toolkit

mcp-toolkit

by Dongnb66

health_ping

Verifies MCP server connectivity by returning service name, version, uptime, Node version, and platform details for health checks.

Instructions

健康检查:返回服务名、版本、运行时长、Node 版本与平台信息,用于验证 MCP 服务器连通性。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "health_ping"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and for a zero-parameter probe it does well: the enumerated return fields make clear that the tool is a read-only informational call with no mutation or side effects. It says nothing about failure behavior, timeouts, or latency when the server is unreachable, which for a connectivity probe is the one behavior an agent might most want.

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?

It is a single sentence that front-loads the action (health check), then lists the returned fields, then states the use case. Every clause earns its place, and there is no filler or redundant restatement of the tool name.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description must, and does, tell the agent what comes back; the enumerated fields substitute adequately for a return-value schema. It falls just short of completeness because a connectivity probe's most important behavior (what an unreachable or degraded result looks like) goes unstated.

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 input schema declares zero properties and the description correspondingly introduces no parameters. With no parameters present, the baseline of 4 applies; there is no parameter semantics for the description to add or omit.

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 names a specific operation (health check / connectivity verification) and enumerates exactly what the response contains: service name, version, uptime, Node version, and platform. This is far more specific than a restated title. It does not explicitly differentiate itself from its siblings, but none of the listed utilities (date_calc, jwt_decode, sqlite_query, etc.) overlap with it, so the gap is minor.

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 closing clause states the call condition directly: use it to verify that the MCP server is reachable. That is clear context for invocation, and no alternative tool could plausibly compete for this job. It stops short of stating when NOT to use the tool (for example, as an application health probe rather than a connectivity check), which would be needed for a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.