Skip to main content
Glama
Huawei DCS MCP
by key-well

ShowInstanceVersion

ShowInstanceVersion
Read-onlyIdempotent

Retrieves the kernel version for a specified cloud Redis instance ID to support read-only troubleshooting and compatibility checks.

Instructions

根据实例ID获取实例内核版本信息(只读查询)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instance_id": "<instance_id>"
    },
    "name": "ShowInstanceVersion"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes实例ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description's only behavioral addition is the parenthetical 只读查询, which largely restates readOnlyHint and says nothing about permissions, per-region behavior, or latency/rate limits of the query. With annotations carrying the burden, this is adequate but adds little.

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 front-loaded sentence with the resource and key parameter stated immediately and zero filler. It is arguably too terse rather than padded, so the only deduction is for lack of any structural elaboration.

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 simple, read-only, single-key lookup with 100% schema coverage, no output schema requirement, and annotations covering safety, the description is nearly sufficient. It would be stronger if it noted what the kernel-version result is useful for or how it differs from ShowInstance, but nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the region and project_id environment-override notes, so the schema already explains all three parameters. The description only echoes that instance_id is the lookup key, adding no syntax, format, or validation detail beyond the schema; baseline 3 applies.

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 states a specific verb (获取/get) and a specific resource (实例内核版本信息/kernel version info) scoped by 实例ID, so an agent knows exactly what it returns. It does not name a sibling to distinguish itself from, e.g. ShowInstance, which returns broader instance details, but the narrow resource scope is clear on its own.

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 call this instead of ShowInstance or ShowInstanceTopology, no prerequisites, and no exclusions. The only implicit cue is the parenthetical 只读查询, which describes the operation type rather than the usage situation.

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