Skip to main content
Glama

get_version_info

Read-only

Fetch implementation and protocol version details to verify compatibility and troubleshoot MCP server integrations.

Instructions

get_version_info Returns: 实现与协议版本信息。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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=true, so the safety profile is covered. The description adds only the content of the return value (implementation and protocol versions), and says nothing about format, latency, or whether the call reaches a remote endpoint despite the openWorld flag.

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?

It is short, but the space is spent poorly: the tool name is repeated verbatim before the only substantive clause, and the answer is partially in Chinese while the rest of the definition is English, which hurts machine readability. The meaningful content ('implementation and protocol version info') is not front-loaded.

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 trivial, zero-parameter, read-only info tool with no output schema, knowing it returns implementation and protocol version info is enough to call it correctly. Only the shape of the returned payload is left implicit, which is acceptable given the tool's simplicity.

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 and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level meaning is missing because no parameters exist.

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?

"Returns: 实现与协议版本信息" does state the resource (implementation and protocol version information), which is more informative than the bare name. However, the sentence opens by redundantly restating the tool name, and the purpose is only loosely specified — an agent cannot tell what distinguishes 'implementation version' from 'protocol version' or in what form they come back.

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 at all: no statement of context, prerequisites, or when another info tool (e.g. a fileset or group info sibling) would be preferred. The agent must infer that this is a general metadata probe purely from the name.

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