Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ShowRocketmqTags

ShowRocketmqTags
Read-onlyIdempotent

Retrieves read-only tags for a specified Huawei RocketMQ instance, enabling label inspection and metadata checks for inventory or 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": "ShowRocketmqTags"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 10。
offsetNo**参数解释**: 偏移量,表示从此偏移量开始查询,offset大于等于0。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 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.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so "(只读查询)" is redundant. The description adds no behavioral context of its own — nothing about pagination behaviour, maximum tags returned, or what happens if the instance has no tags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short phrase, so nothing is wasted, but it is under-specified rather than efficient — there is no front-loaded detail beyond the name restated in Chinese.

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 tool with five parameters and no output schema, the description says nothing about the shape of the returned tags, ordering, or how limit/offset interact with the result set. An agent could call it correctly only because the schema is fully documented, not because the description is complete.

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%: limit, offset, region, project_id, and instance_id all carry detailed descriptions in the schema, including how to obtain instance_id. The description contributes no additional meaning about these parameters, 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 names a specific verb and resource ("查询实例标签"), so the agent knows this returns tags for an instance. However, it does not distinguish this from the sibling ShowRocketmqProjectTags, which reads project-level tags, leaving ambiguity about scope that only the instance_id parameter resolves.

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, and no mention of alternatives such as ShowRocketmqProjectTags. The parenthetical "只读查询" only repeats the safety profile already given by the annotations rather than helping an agent choose this tool.

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