Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ListRocketInstanceTopics

ListRocketInstanceTopics
Read-onlyIdempotent

Queries the topic list for a specified Huawei RocketMQ instance by instance ID, with optional limit and offset for pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 1~50。 **默认取值**: 不涉及。
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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description's "只读查询" merely repeats readOnlyHint and adds nothing further — no pagination behavior, no scoping to the instance, no notes on result size or ordering.

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 short phrase with zero wasted words and the read-only cue front-loaded. It is efficient, though the brevity is under-specification rather than true economy of expression.

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 five-parameter paginated listing tool with no output schema, the description says nothing about result shape, pagination semantics, or required instance scoping that an agent needs to invoke it confidently. The rich schema partially compensates, but the description itself is far too thin for this complexity.

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%, with limit, offset, region, project_id and instance_id all documented inline in the schema, so the baseline of 3 applies. The description contributes no additional meaning about how limit/offset interact or what region/project_id overriding implies.

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 Chinese phrase "查询主题列表" supplies a verb (query) and resource (topic list), and the parenthetical marks it read-only. However, it largely restates what the tool name ListRocketInstanceTopics already conveys, and it never distinguishes this listing from siblings such as ListInstances or ListConsumerGroupOfTopic.

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 statement of when to use this tool, when not to, or which sibling to prefer for related queries. The only guidance is the parenthetical "只读查询", which implies a safe read but does not route the agent among alternatives.

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