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

ShowReplicationStates

ShowReplicationStates
Read-onlyIdempotent

Retrieve read-only replica states for a specified Redis instance shard to diagnose replication health and synchronization issues.

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>",
      "group_id": "<group_id>"
    },
    "name": "ShowReplicationStates"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
group_idYes分片ID。
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 read-only parenthetical in the description merely restates structured data. Nothing is added about what a replica state contains, whether replicas must exist for an error, or how lag/health is represented in the result.

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?

Two short fragments with no filler and the read-only signal front-loaded, so nothing is wasted. The trade-off is that the brevity comes from under-specification rather than tight editing – the size is small but so is the information delivered.

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 tool requiring both an instance and a shard/group identifier and returning replica state with no output schema, the description never explains what is returned or what a valid state looks like. The only real behavior it pins down, read-only access, is already in the annotations, leaving the agent under-equipped for a non-trivial two-key lookup.

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 and group_id documented in-schema and region/project_id flagged as environment overrides, so the schema carries parameter meaning on its own. The description contributes nothing beyond that baseline, which is exactly the minimum-viable 3 when the schema is fully documented.

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 ("获取副本状态" – get replica status), so the basic purpose is recoverable. However, it gives no scope or differentiator against look-alike siblings such as ListGroupReplicationInfo or ShowInstanceTopology, which also return replication-related state, so an agent cannot confidently choose between them from the description alone.

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 guidance on when to call this tool, when not to, or which sibling to prefer for related replication information. The parenthetical "(只读查询)" signals safety, not usage; the agent is left to infer the trigger condition from the tool name.

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