Skip to main content
Glama

sdk_health

Retrieve a bot health summary covering SDK version, uptime, loaded module count, adapter statuses, event buffer, and subscription details to assess runtime status.

Instructions

机器人健康摘要:SDK 版本、运行时长、已加载模块数、各适配器状态、事件缓冲与订阅情况。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. '健康摘要' strongly implies a passive read, and the enumerated contents tell the agent what data surfaces, but side effects, cost, and permissions are never stated. The existing output schema covers the return shape, which lowers the remaining gap.

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?

A single sentence with the resource type front-loaded and the payload contents listed after a colon. Every element 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?

For a zero-parameter read tool with an output schema, the description is nearly complete: it enumerates the content areas an agent can expect. The only shortfall is that it never frames this as the aggregate overview relative to the per-adapter and per-module siblings, which matters given how many similar tools exist.

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 there is nothing for the description to disambiguate at the argument level. Baseline 4 applies; the description correctly avoids inventing parameters that the empty schema does not define.

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 resource ('机器人健康摘要') and enumerates exactly what the summary contains: SDK version, uptime, loaded module count, per-adapter status, event buffer and subscription state. That lets an agent tell it apart from more granular siblings like get_adapter_status or get_module_info. It stops short of explicitly naming those siblings as alternatives, so a 4 rather than a 5.

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 guidance, no mention of when to prefer this aggregate over get_adapter_status or get_module_info, and no stated prerequisites. The agent can infer it is a diagnostic overview, but the description does nothing to route between this tool and its many siblings.

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