Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ListTopicAccessPolicy

ListTopicAccessPolicy
Read-onlyIdempotent

Queries the authorized user list and access policy for a RocketMQ topic by instance ID to audit or troubleshoot topic permissions.

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>",
      "topic": "<topic>"
    },
    "name": "ListTopicAccessPolicy"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo**参数解释**: 查询数量。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
topicYes**参数解释**: 主题名称。 **约束限制**: 不涉及。 **取值范围**: 不涉及。 **默认取值**: 不涉及。
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.9/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, so the description's '(只读查询)' restates structured data rather than adding context. Nothing is disclosed about pagination behavior, result ordering, or what happens when the topic has no policy. The description adds essentially no behavioral value beyond the annotations.

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 sentence with the resource front-loaded and no filler wording. It is efficient, though its brevity leaves the definition thin rather than being padded with waste. Nothing needs to be removed; more needs to be added.

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?

For a six-parameter read-only list tool with no output schema, the description covers the core purpose but omits pagination expectations and any note on return contents. Because the schema is fully documented and annotations cover the safety profile, the gaps are moderate rather than critical. An agent could call it correctly but would learn nothing about what comes back.

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 every parameter including instance_id, topic, limit, offset, region, and project_id documented in the schema itself. The description adds no meaning about which parameters scope the query or how limit/offset interact. Baseline 3 is appropriate when the schema carries the full parameter burden.

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 states a specific verb and resource: querying the list of authorized users for a topic. This is clear enough that an agent can distinguish it from status or detail siblings such as ShowTopicStatus or ShowOneTopic. It does not explicitly name the closest sibling, ListConsumeGroupAccessPolicy, so it misses the sibling-differentiation bar for a 5.

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?

The description contains no when-to-use guidance, no prerequisites, and no pointer to alternatives. It does not say when an agent should call this instead of ListConsumeGroupAccessPolicy, which is the nearest competing access-policy lister. The parenthetical '只读查询' describes a property, not a usage condition.

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