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

ListGroupReplicationInfo

ListGroupReplicationInfo
Read-onlyIdempotent

Query read-only shard and group replication details for a specified Huawei DCS Redis instance to inspect replication topology and status.

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

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.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the description's parenthetical 只读查询 adds nothing. It says nothing about what the shard/group replication data contains, whether the result is paginated, or what permissions are needed.

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?

At eight characters there is no wasted wording, but the brevity reflects under-specification rather than disciplined editing. There is no structure to front-load because there is essentially no content.

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?

For a read-only list tool whose schema fully documents all three parameters, the description is still too thin: it does not clarify what 分片 (shard group) means here, what is returned, or how it differs from the sibling replication/state tools. With no output schema, the description should carry more of that burden.

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%, with instance_id, region, and project_id all documented in-schema, so the baseline is 3. The description adds no meaning beyond the schema, such as whether instance_id must be a cluster instance or how region/project overrides interact.

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 states a verb and a resource in Chinese: 查询 (query) shard information. That is a real purpose statement, not pure tautology, but it is generic and does not distinguish this tool from close siblings such as ShowReplicationStates or ShowInstanceTopology, which an agent could easily confuse it with.

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 signal, 只读查询 (read-only query), is a restatement of the readOnlyHint annotation rather than a selection criterion. There is no statement of when to choose this over ShowReplicationStates or any other sibling, and no prerequisites are given.

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