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

ListAvailableZones

ListAvailableZones
Read-onlyIdempotent

Retrieves available zones for Huawei Cloud DCS Redis instances, optionally overriding region and project ID, to support read-only deployment and troubleshooting checks.

Instructions

查询可用区信息(只读查询)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ListAvailableZones"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, and the description's "(只读查询)" merely restates the read-only flag. It adds no new behavior such as scope of zones returned, whether region/project default from environment variables when omitted, or cost/latency characteristics of an open-world lookup.

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 description is a single short phrase and is front-loaded with the resource, which is good, but the trailing parenthetical duplicates annotation information and the remaining brevity comes at the cost of substantive detail rather than from tight editing.

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 simple two-optional-parameter read tool with no output schema and rich annotations, the definition still leaves gaps an agent would care about: which region's zones are listed when region is omitted, and what the zone records contain. The description is complete only in the narrowest sense of naming the operation.

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 coverage is 100%: both region and project_id are documented in the schema as overriding HUAWEI_REGION and HUAWEI_PROJECT_ID. The description adds no meaning about how these parameters shape the result set (e.g. whether a zone list differs per region), so the baseline 3 applies.

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?

The description names a specific verb ("查询"/query) and resource ("可用区"/availability zones), which is distinct from sibling tools that deal with instances, clients, logs and configurations. It does not explicitly contrast itself with any sibling, but the resource is unambiguous enough that an agent can identify the operation.

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 versus alternatives, nor any stated prerequisite such as looking up zones before creating an instance. The only usage hint is the parenthetical "只读查询", which describes the operation type rather than a situation in which to use it.

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