Skip to main content
Glama

runtime_info

Read-only

Reads active MCP version, startup implementation fingerprint, disk differences, tool inventory fingerprint, and RP9 template availability, then indicates whether a service reconnect is needed.

Instructions

读取活动 MCP 版本、启动实现指纹、磁盘差异、工具清单指纹及 RP9 模板可用性;判断是否需要重新连接服务。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description adds value by enumerating the diagnostic surface (fingerprints, disk diff, template availability), but says nothing about cost, side effects on the MCP connection, or how the result should be interpreted beyond a reconnect decision.

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?

A single semicolon-delimited sentence: the list of what is read comes first, the decision it supports comes last, so it is front-loaded and free of filler. It is dense enough that a reader must parse five parallel noun phrases, but no sentence is wasted.

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-only diagnostic with no output schema, the description covers what the agent needs: what data is gathered and what decision it supports. The one gap is that the shape of the returned report is not described, so the agent knows what is collected but not how it will be presented.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The enumerated read items effectively document the only input, which is none.

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 (读取/read) and enumerates exactly what is read: active MCP version, startup implementation fingerprint, disk diff, tool-list fingerprint, and RP9 template availability. No sibling tool performs a runtime diagnostic, so this is easy to distinguish in the catalog, though the name 'runtime_info' alone would have been far less informative.

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?

The closing clause '判断是否需要重新连接服务' implies the intended use — checking whether a reconnect is needed — which gives the agent a usable trigger. It stops short of stating when NOT to call it, what to do with the result, or naming any alternative diagnostic tool.

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