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

ShowInstance

ShowInstance
Read-onlyIdempotent

Queries a specified Huawei Cloud Redis instance in read-only mode to inspect status and support troubleshooting without changing resources.

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

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so "只读查询" adds nothing beyond structured data. The description says nothing about permissions, region/project override behavior, error cases for a missing instance, or the shape of the response, which is the context an agent actually lacks.

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?

The single short phrase contains no filler, but it is under-specified rather than efficient: nothing is front-loaded because there is nothing else. It could carry one more clause (what is returned or when to prefer it) at almost no cost.

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?

There is no output schema, so the description should say what a "show" returns, and it does not. Combined with absent usage guidance, an agent knows only that this is a read on one instance, which is thin for a tool whose siblings overlap heavily.

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 the schema itself explains that region and project_id override HUAWEI_REGION/HUAWEI_PROJECT_ID and that instance_id is the instance identifier. The description adds no meaning beyond that, so the baseline of 3 applies.

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 phrase "查询指定实例" names a verb (query) and a resource (a specified instance), which is enough to separate it in spirit from ListInstances. However, it never states which attributes of the instance are returned or how it differs from siblings such as ShowInstanceTopology or ShowInstanceVersion, so an agent must guess at the boundary.

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 prerequisites (for example, whether the instance must exist or be running), and no reference to alternatives like ListInstances. The only hint is the parenthetical "只读查询", which merely restates that it is a read operation.

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