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

ListClients

ListClients
Read-onlyIdempotent

Retrieve read-only client connection sessions for a Huawei DCS Redis instance, with filters for client address, node, sorting, and pagination to support connection troubleshooting.

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

Input Schema

NameRequiredDescriptionDefault
addrNo按客户端连接地址过滤。
sortNo排序字段。
limitNo每页显示条数,最小值为1,最大值为1000,若不设置该参数,则为10.
orderNo排序方式
offsetNo偏移量,表示从此偏移量开始查询, 偏移量大于等于0。
regionNoOverrides HUAWEI_REGION.
node_idNo节点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, openWorldHint=true and destructiveHint=false, so the description's '(只读查询)' simply restates structured data. Nothing is added about pagination behavior, default page size, or what happens with large result sets on a 9-parameter listing tool.

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?

It is a single short phrase with no padding, but the only secondary clause duplicates the annotations, and the extreme brevity leaves the definition under-specified rather than efficiently concise.

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 9-parameter listing tool with filtering, sorting and pagination, and with no output schema, the description says almost nothing about return content, ordering defaults, or how filters combine. The schema compensates for parameters, but overall context remains thin.

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%, so every parameter (addr, sort, limit, order, offset, region, node_id, project_id, instance_id) is already documented in the schema. The description contributes no additional parameter meaning, which matches the baseline 3 for fully covered schemas.

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 resource ('获取会话列表' – get session list), but the resource wording ('会话'/sessions) does not match the tool name ListClients, leaving ambiguity about whether these are client connections or sessions. It never distinguishes this from sibling list tools such as ListInstances or ListMonitoredObjects.

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 the many other List* siblings, and no mention of prerequisites such as needing an instance_id. The parenthetical '只读查询' is a safety note, not usage guidance.

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