Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ShowRocketmqProjectTags

ShowRocketmqProjectTags
Read-onlyIdempotent

Retrieve read-only project tags for Huawei RocketMQ to inspect cloud resources by project, with pagination via limit and offset.

Instructions

查询项目标签(只读查询)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ShowRocketmqProjectTags"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 10。
offsetNo**参数解释**: 偏移量,表示从此偏移量开始查询。 **约束限制**: 不涉及。 **取值范围**: 大于等于0。 **默认取值**: 0。
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_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, destructiveHint=false, and openWorldHint=true; the description's parenthetical '只读查询' merely repeats the read-only hint without adding context. It says nothing about pagination behavior for the limit/offset pair, result ordering, or whether tags are scoped to a project or region.

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?

It is a single short clause with no wasted words, so it is concise, but the brevity comes at the cost of substance: there is no front-loaded statement of scope, return content, or paging behavior. Brevity here reads as under-specification rather than disciplined editing.

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?

The tool takes four parameters and returns tag data with no output schema, yet the description says nothing about the shape of the result, pagination semantics, or how region/project_id are resolved. For a query tool whose annotations already cover the safety profile, this leaves the agent with unreplaced gaps.

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 the schema already documents limit, offset, region, and project_id, and the baseline is 3. The description adds no meaning beyond the schema — notably it does not explain the region/project_id override behavior or how paging interacts with the tag list.

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 ('查询项目标签(只读查询)') restates the tool name in Chinese with a parenthetical, so it identifies the resource (project tags) and the operation (query) but adds little beyond the title 'ShowRocketmqProjectTags'. It gives no basis for distinguishing this from the sibling ShowRocketmqTags, which is likely a closely related tag query.

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 mention of when to prefer this over ShowRocketmqTags or the other Show* query tools, and no prerequisites or exclusions. The only hint is '(只读查询)', which describes the operation mode rather than the choice context.

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