Skip to main content
Glama

VibeGuard 健康检查

health

Reports MCP shell, state repository, configuration, credential, and downstream tool status. Use it to diagnose online, degraded, offline, or unused tools, latency, and expiration issues.

Instructions

报告 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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the scope and structure of what is inspected (tool list, state directory, state files, credential expiry, online/degraded/offline/unused + latency), which is genuinely useful context. However, it never states that the call is read-only and side-effect free, nor whether probing downstream tools incurs latency, network calls, or rate limits — meaningful gaps for a diagnostic tool with zero annotation coverage.

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

Conciseness4/5

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

One dense sentence that front-loads the purpose and then lists the covered surfaces in a scannable order. Every clause corresponds to a real reported area, so nothing is filler, though the colon-and-commas enumeration is heavy enough to be slightly harder to parse than a short bulleted structure would be.

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?

There is no output schema, so the description must convey what comes back — and it does, enumerating state directory, state files, credential expiry, per-tool status enum values and latency. For a zero-parameter diagnostic tool that is close to sufficient; only the safety/latency profile of running the check is left unaddressed.

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 no parameters, so the baseline of 4 applies. The description correctly implies invocation is argument-free and spends no words on phantom inputs.

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 opens with a specific verb (报告/report) and resource (健康状态) and then enumerates exactly what is covered: the MCP shell, state repository, configuration, credential expiry and downstream tool health. This is far more specific than a bare 'health check' and lets an agent distinguish it from sibling actions like clarify/review/test, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the diagnostic probe to call when verifying environment or dependency status, but there is no explicit 'call this when…' clause, no when-not guidance, and no mention of whether it should precede or follow other operations. The mention of orchestrator-visible downstream health hints at the diagnostic use case but does not direct invocation.

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