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

ShowNodesInformation

ShowNodesInformation
Read-onlyIdempotent

Retrieves node details for a specified Redis instance using its ID, enabling read-only troubleshooting of shard and node configuration.

Instructions

查询实例节点信息(只读查询)

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

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

C2.6/5.0
Behavior2/5

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

The phrase 只读查询 restates the annotations' readOnlyHint=true and destructiveHint=false; it adds nothing beyond them. It also says nothing about the scope of the response, pagination, or whether the tool can be called on behalf of other projects.

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?

The definition is a single short sentence and is front-loaded. It has no filler, but its brevity leaves the purpose thin rather than dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should at least indicate what node information is returned: role, status, node ID. It does not, leaving an agent unable to predict the result of the call.

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% and each parameter is documented, so the baseline a score of 3 is correct. The description adds no extra detail about instance_id, region, or project_id.

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?

The description names a specific verb and resource: 查询 (query) 实例节点信息 (instance node information). However, it never distinguishes this tool from the sibling BatchShowNodesInformation, so an agent cannot tell whether to call this tool alone or in a batch.

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?

The only usage cue is the parenthetical 只读查询. The description gives no guidance about when to call this tool rather than ShowInstance, ShowInstanceTopology, or BatchShowNodesInformation.

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