Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ShowConsumerConnections

ShowConsumerConnections
Read-onlyIdempotent

Lists consumer connections for a specified RocketMQ instance and consumer group, supporting read-only inspection of connected clients and 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>",
      "group": "<group>"
    },
    "name": "ShowConsumerConnections"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYes**参数解释**: 消费组名称。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 1~50。 **默认取值**: 不涉及。
offsetNo**参数解释**: 偏移量,表示从此偏移量开始查询, offset大于等于0。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
regionNoOverrides HUAWEI_REGION.
is_detailNo**参数解释**: 是否查询消费者详细列表,参数为“true”则表示查询详细列表,否则表示查询简易列表。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes**参数解释**: 实例ID。获取方法如下:调用“查询所有实例列表”接口,从响应体中获取实例ID。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 '(只读查询)' merely restates what structured data provides. With annotations covering the safety profile, the description should have added context such as pagination behavior (limit 1~50), what is_detail changes in the response, or ordering, but it adds nothing.

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 zero filler, and the read-only qualifier is placed up front. It is not padded, though the brevity comes at the cost of substance addressed in the other dimensions.

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 7-parameter paginated query tool with no output schema, the description is far too thin: it never explains paging limits, the is_detail simple/detailed switch, or the region/project_id override behavior. An agent can only call this correctly by reading the schema alone.

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 all seven parameters, including the meaning of is_detail and the limit/offset paging, are already documented in the schema. The description adds no parameter meaning beyond the schema, which is the expected baseline of 3 when the schema does the heavy lifting.

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 names a specific resource (consumer list / 消费者列表) and a verb (查询), so the basic purpose is clear. However, it gives no way to distinguish this tool from close siblings such as ShowConsumerListOrDetails or ListInstanceConsumerGroups, and the tool name 'ShowConsumerConnections' suggests connections rather than a list, which the description does not reconcile.

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 indication of when to use this tool versus the many sibling listing tools, and no preconditions are stated beyond the required instance_id and group. The only guidance is the parenthetical '(只读查询)', which describes safety rather than usage context.

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