Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ListConsumerGroupOfTopic

ListConsumerGroupOfTopic
Read-onlyIdempotent

Lists the consumer groups associated with a specified topic in a RocketMQ instance, enabling read-only inspection and troubleshooting of group subscriptions.

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>",
      "topic": "<topic>"
    },
    "name": "ListConsumerGroupOfTopic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo**参数解释**: 当次查询返回的最大个数。 **约束限制**: 不涉及。 **取值范围**: 1~50。 **默认取值**: 10。
topicYes**参数解释**: 主题名称。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
offsetNo**参数解释**: 偏移量,表示从此偏移量开始查询。 **约束限制**: 不涉及。 **取值范围**: 大于等于0。 **默认取值**: 不涉及。
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes**参数解释**: 实例ID。获取方法如下:调用“查询所有实例列表”接口,从响应体中获取实例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 parenthetical '只读查询' merely restates the readOnly annotation rather than adding context. It says nothing about pagination behaviour (limit/offset), result ordering, or whether groups from all instances are included, which are the behaviors an agent would actually need beyond the annotations.

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?

It is a single short sentence with zero filler and the resource is front-loaded. However, the terseness crosses into under-specification for a six-parameter paginated query, so it is not maximally well-sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input schema is fully documented and annotations cover the safety profile, and there is no output schema the description would need to explain. What is still missing for a paginated list operation is any guidance on paging through results or what the returned list contains, leaving a modest 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%, so every parameter, including limit, offset, topic, instance_id and the region/project_id overrides, is already documented in the schema. The description adds no syntax, defaulting or pagination semantics beyond that, so the baseline of 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 states a specific verb and resource: query the consumer-group list of a given topic, and flags it as a read-only query. That is enough for an agent to know what the tool returns the identities of, though it never distinguishes itself from siblings such as ListInstanceConsumerGroups or ShowConsumerListOrDetails.

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 when-to-use guidance, no statement of prerequisites (e.g. that a valid instance_id must first be obtained), and no pointer to alternative tools for related lookups. The agent is left to infer usage purely from the tool name.

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