Skip to main content
Glama
iKuai MCP Server
by gxxHuang

Run Router Health Report

run_router_health_report
Read-only

Generates a health report for the iKuai router, checking system status, connectivity, and security to detect and report issues.

Instructions

运行路由体检

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": "run_router_health_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, so safety is covered. But a "router health check" is plausibly a long-running, resource-intensive diagnostic, and the description says nothing about execution time, whether results are synchronous, or what the check actually probes. For a no-parameter diagnostic tool this is a meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single phrase is concise and front-loaded with no filler, which is good. But it is under-specified rather than efficiently sized: one short phrase cannot carry the behavioral weight this tool needs, and it is written only in Chinese without an English gloss.

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?

An output schema exists, so the description needn't explain return values, and there are no parameters to document. Still, for a diagnostic trigger the description should say at minimum whether the report runs synchronously and roughly what it summarizes; that context is entirely absent.

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 takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no inputs are required, and there is no parameter syntax it needs to compensate for.

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?

"运行路由体检" names a verb (run) and resource domain (router health check), so the agent can infer the general action. However, it gives no detail on what the health check covers and does not distinguish itself from nearby siblings such as get_health_check_config or get_system_overview, both of which could plausibly be what an agent wants for health information.

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?

There is no when-to-use or when-not-to-use guidance whatsoever. The agent is not told whether this is a read-only diagnostic to call proactively or a heavier operation reserved for troubleshooting, nor how it relates to get_health_check_config, which appears to configure rather than run the check.

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

Deploy Server

Other Tools