Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ListConsumeGroupAccessPolicy

ListConsumeGroupAccessPolicy
Read-onlyIdempotent

Retrieve authorized users for a RocketMQ consumer group with read-only queries, helping audit group permissions and verify access controls.

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": {
      "engine": "<engine>",
      "instance_id": "<instance_id>",
      "group": "<group>"
    },
    "name": "ListConsumeGroupAccessPolicy"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYes**参数解释**: 消费组。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
engineYes**参数解释**: 消息引擎。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: rocketmq。
offsetNo**参数解释**: 偏移量,表示从此偏移量开始查询, offset大于等于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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the '(只读查询)' note in the description simply repeats structured data. The description adds nothing beyond the annotations: no pagination behavior, no permission or authorization requirements, and no indication of what the returned ACL entries contain.

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?

The description consists of a single short sentence, with the primary purpose front-loaded and no wasted wording. It is arguably over-terse for a 7-parameter listing tool, but nothing is redundant or poorly structured.

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?

For a read-only listing tool with 7 parameters and no output schema, the description is only minimally sufficient: it says what is queried but not what the response contains, how pagination should be applied to limit/offset, or how the result differs from ListTopicAccessPolicy. The annotations and full schema coverage compensate for part of this 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 engine, instance_id, group, limit, and offset, is already documented in the schema, and the description adds no further meaning. A baseline of 3 is appropriate because the schema carries the parameter burden, although the description does not clarify the limit/offset pagination contract.

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 uses a specific verb and resource in Chinese: querying the authorized user list of a consumer group. This is clear enough that an agent knows what the tool returns. However, it does not distinguish itself from the near-identical sibling ListTopicAccessPolicy, which is replacement of one dimension (topic vs. consumer group) away.

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?

The description contains no when-to-use guidance, no prerequisites, and no exclusions. The only hint is the parenthetical '(只读查询)' clarifying that this is read-only, and the sibling tools provide no explicit routing either. An agent must infer usage from the name alone.

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