Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ShowConsumerListOrDetails

ShowConsumerListOrDetails
Read-onlyIdempotent

Retrieves the list of topics consumed by a specified consumer group, or detailed information for a given topic, using read-only queries on Huawei RocketMQ instances.

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

Input Schema

NameRequiredDescriptionDefault
groupYes**参数解释**: 消费组名称。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
limitNo**参数解释**: 当次查询返回Topic的最大个数。 **约束限制**: 不涉及。 **取值范围**: 1~50。 **默认取值**: 10。
topicNo**参数解释**: 待查询的Topic,不指定时查询Topic列表,指定时查询详情。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
offsetNo**参数解释**: 偏移量,表示从此偏移量开始查询。 **约束限制**: 不涉及。 **取值范围**: 大于等于0。 **默认取值**: 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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, and the parenthetical "(只读查询)" merely restates readOnlyHint rather than adding new information. Nothing is disclosed about what the two modes actually return, pagination behavior, or permission requirements, though it does not contradict 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short and front-loaded with no wasted words, but the brevity reflects under-specification rather than disciplined trimming. A single vague clause is not an appropriate size for a seven-parameter tool with two behavioral modes.

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 seven-parameter tool with two distinct modes (list vs. detail, driven by the topic parameter) and no output schema, the description should clarify what entity is returned and how the modes differ. It leaves the central subject of the query undefined and offers nothing about results, so an agent must infer the tool's scope entirely from the schema.

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 instance_id, group, topic, limit, and offset — are already fully documented in the schema, including the topic-driven list-vs-detail switch. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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?

Names a verb (查询) and a dual scope (列表或详情), which loosely matches the schema's topic-optional list/detail behavior. However, "消费" is ambiguous — it is unclear whether this returns consumer groups, consumers, or topic consumption details — and nothing distinguishes it from siblings such as ShowGroup or ListInstanceConsumerGroups.

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?

Gives no indication of when to use this tool versus the many sibling list/show tools, and states no prerequisites or exclusions. The only implied usage comes from the schema's topic parameter, not from the description itself.

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