Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ListBrokers

ListBrokers
Read-onlyIdempotent

Queries the broker list of a specified RocketMQ instance with offset and limit pagination. Use it to review broker nodes and topology for read-only inspection 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>"
    },
    "name": "ListBrokers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
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.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, and the description's "(只读查询)" merely repeats that. It adds nothing about pagination behavior for limit/offset, per-instance scoping, or result shape. With annotations covering the safety profile, the description earns only the minimum because it contributes no new behavioral context.

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 definition is a single short phrase with no filler and the resource is front-loaded. Its brevity borders on under-specification, but nothing is redundant.

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?

This is a five-parameter, paginated, per-instance listing tool with no output schema and no annotations explaining return values. A seven-character description cannot convey the required instance_id, how limit/offset interact, or what the broker list contains, so an agent must reverse-engineer intent from schema and name 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 five parameters are already documented in the schema, including instance_id lookup instructions and offset semantics. The description adds no meaning 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a query verb with a resource ("查询代理列表"), so the basic intent is recoverable. However, "代理" is ambiguous outside the RocketMQ context (broker vs. proxy/agent), and the description never says the scope is one instance, which is the required parameter. As a result, an agent cannot fully separate this from siblings like ListInstances or ShowInstanceNodes based on the description alone.

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 prerequisites stated (such as needing an instance_id obtained from ListInstances), and no mention of alternatives. The only usage signal is the parenthetical "只读查询", which restates safety rather than selection criteria.

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