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

ListConfigurations

ListConfigurations
Read-onlyIdempotent

Queries configuration parameters for a specified Huawei Cloud Redis instance in read-only mode, helping troubleshoot instance settings without modifying 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": "ListConfigurations"
  }
}

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's '只读查询' merely restates that. It adds no context beyond the annotations, such as whether all parameters are returned or whether defaults/modified flags are included; there is no contradiction, but also no incremental disclosure.

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 short phrase with no redundant wording, and the core purpose is front-loaded. It is efficient rather than padded, though its brevity borders on under-specification.

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 something about what comes back — the parameter list shape, whether it is paginated or bounded, or how it relates to ListConfigHistories. For a list tool with zero return-value documentation and no output schema, this is a meaningful gap.

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 region, project_id and instance_id all documented in the schema itself, so the baseline is 3. The description contributes nothing extra about these parameters (e.g. that region/project_id override environment defaults).

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?

Names a specific verb (查询/query) and resource (实例配置参数/instance configuration parameters), which is more precise than the tautological title 'ListConfigurations'. It does not, however, distinguish itself from near-neighbours such as ListConfigHistories or ShowInstance, so the agent must infer 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?

The only usage signal is the parenthetical '(只读查询)', which says nothing about when to prefer this over ListConfigHistories (parameter change history) or ShowInstance (instance metadata). No prerequisites, exclusions, or alternative routing are stated.

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