Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ListRocketMqMigrationTask

ListRocketMqMigrationTask
Read-onlyIdempotent

Queries all migration tasks for a RocketMQ instance or retrieves details for a specified task, enabling read-only migration status 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": "ListRocketMqMigrationTask"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo**参数解释**: 任务ID。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
nameNo**参数解释**: vhost名称 **约束限制**: - 查询vhost列表时,该字段可为空。 - 查询exchange列表时,该字段为exchange所属vhost名称。 - 查询queue列表时,该字段为queue所属vhost-所属exchange,例vhost1-exchange1。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
typeNo**参数解释**: 查询类型。 **约束限制**: 不涉及。 **取值范围**: - vhost:虚拟主机。 - exchange:交换机。 - queue:队列。 - all:所有。 **默认取值**: 不涉及。
limitNo**参数解释**: 当前页大小。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
offsetNo**参数解释**: 当前页,从1开始。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
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

B3.2/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 and destructiveHint=false, and the description's parenthetical '(只读查询)' merely repeats that. Beyond restating the safety profile, it discloses nothing about pagination defaults, result ordering, empty-result behavior, or the scope of 'instance' relative to the region/project_id overrides present in the schema.

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?

A single short sentence with the primary scope ('查询实例下所有迁移任务') front-loaded before the narrower variant. Nothing is padded, though the parenthetical read-only note is redundant with the annotations and could be dropped.

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?

With no output schema, the description carries some burden to indicate what comes back, but it says nothing about the returned task list shape, total counts, or pagination semantics for limit/offset. For a read-only list tool with fully documented parameters and rich annotations this is adequate but leaves real gaps for an agent assembling a call.

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 coverage is 100%, so all eight parameters are documented in the schema and the baseline is 3. However, the description adds no parameter meaning at all, and it does not reconcile the 'migration task' framing with schema parameters such as name/type that describe vhost/exchange/queue filters, leaving an agent to work that out from the schema alone.

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 gives a specific verb and resource ('查询' + '迁移任务') and states the two modes: all migration tasks under an instance, or a single task's details. It is clearly distinguishable from siblings like ListInstances or ShowGroup, which cover different resources, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'all vs. specified' split implies that supplying a task ID narrows the query, but this is left implicit rather than stated as a rule. There is no guidance on when to prefer this tool over other RocketMQ listing tools, nor on how pagination parameters should be combined with the filter parameters.

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