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

ListInstances

ListInstances
Read-onlyIdempotent

Retrieves a paginated list of cloud Redis instances and filters them by ID, name, region, status, or tags for read-only inventory and troubleshooting.

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

Input Schema

NameRequiredDescriptionDefault
ipNo连接缓存实例的IP地址。
nameNo实例名称。
tagsNo根据实例标签键值对进行查询。{key}表示标签键,{value}表示标签值。 如果同时使用多个标签键值对进行查询,中间使用逗号分隔开,表示查询同时包含指定标签键值对的实例。
limitNo每页显示条数,最小值为1,最大值为1000,若不设置该参数,则为10。
offsetNo偏移量,表示从此偏移量开始查询, offset大于等于0
regionNoOverrides HUAWEI_REGION.
statusNo实例状态。详细状态说明见[缓存实例状态说明](https://support.huaweicloud.com/api-dcs/dcs-api-0312047.html)
name_equalNo是否按照实例名称进行精确匹配查询。 和name字段对应,name字段为模糊匹配的用例名,name_equal是精确匹配的用例名。
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idNo实例ID。
include_deleteNo是否返回已删除的实例数。 当参数值为“true”时,返回已删除的实例数。参数值为“false”或者其他值,不返回已删除的实例数。
include_failureNo是否返回创建失败的实例数。 当参数值为“true”时,返回创建失败的实例数。参数值为“false”或者其他值,不返回创建失败的实例数。

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, and destructiveHint=false, so the parenthetical '(只读查询)' merely repeats structured data. The description adds no behavior beyond the annotations — nothing about default page size, result ordering, or how the many filters combine.

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 with no wasted wording, which is structurally front-loaded. But it is brief to the point of under-specification, and the trailing parenthetical is redundant with the annotations rather than informative.

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?

The tool is a 12-parameter paginated list query with no output schema, yet the description says nothing about filtering semantics, pagination defaults, or what the response contains. For this level of complexity, one sentence restating that it is a read query is not sufficient.

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 all 12 parameters individually documented in the schema (including ambiguity-prone ones like name vs name_equal and include_delete/include_failure). The description adds no parameter meaning beyond the schema, so the baseline 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 description states a clear verb and resource ('查询所有实例列表' / query all instance list), so the basic operation is identifiable. However, the word '所有' (all) is misleading given the 12 filtering parameters, and nothing distinguishes it from siblings such as ShowInstance or ListConfigurations, which an agent would need to choose between.

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 use this tool versus alternatives. The agent is not told the difference between ListInstances and ShowInstance, nor whether ListInstances should be used only for browsing or also for looking up a specific instance.

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