Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ShowGroup

ShowGroup
Read-onlyIdempotent

Retrieve read-only details for a specified RocketMQ consumer group by instance ID and group name to inspect configuration and troubleshoot consumption issues.

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

Input Schema

NameRequiredDescriptionDefault
groupYes**参数解释**: 消费组名称。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
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.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, destructiveHint=false, and openWorldHint=true, so the description's "只读查询" merely restates structured data. Nothing is added about what the response contains, whether a wrong instance_id or group name errors out, or what permissions are required.

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 is a single compact phrase with no padding, and the read-only qualifier is placed immediately after the core purpose. Its brevity comes at the cost of detail rather than verbosity.

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?

There is no output schema, so the description needs to describe the return value of a lookup tool, and it does not. For a tool that fetches a specific consumer group by instance_id and group, an agent cannot know what fields to expect or how a not-found case is handled.

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?

All four parameters carry schema descriptions (100% coverage), including how to obtain instance_id and the region/project_id override semantics, so the schema does the work. With full schema coverage, this dimension sets the baseline at 3.

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 gives a specific verb and resource ("查询指定消费组"), which is clearer than the name alone, but it does not distinguish this tool from nearby siblings such as ListInstanceConsumerGroups, ListConsumerGroupOfTopic, or ShowConsumerListOrDetails. An agent cannot tell from the text which of these consumer-group tools to pick.

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 only guidance offered is the parenthetical "只读查询" (read-only query). There is no statement of when to use this tool versus the sibling list tools that also return consumer-group data, and no prerequisites or exclusions are named.

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