Skip to main content
Glama
Huawei RocketMQ MCP

Huawei RocketMQ MCP

by key-well

ShowInstance

ShowInstance
Read-onlyIdempotent

Retrieves read-only details for a specified Huawei RocketMQ instance, helping inspect configuration and status for troubleshooting without modifying resources.

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

Input Schema

NameRequiredDescriptionDefault
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.7/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, destructiveHint=false, and openWorldHint=true, so the description's '(只读查询)' merely repeats structured data. No additional behavior is disclosed, such as whether a non-existent instance errors or returns empty, or any permission requirements.

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 phrase with zero waste and the core intent is front-loaded, but brevity here comes at the cost of under-specification rather than disciplined economy. Nothing is padded, yet almost nothing is conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-resource read tool, the annotations fully cover the safety profile and the schema fully documents all three parameters, so the description is nearly sufficient. The only gap is that with no output schema, the agent learns nothing about what instance attributes the response contains.

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%: instance_id includes a detailed explanation of how to obtain it, and region/project_id document their environment-variable overrides. The description adds no parameter meaning beyond the schema, so the baseline 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 states a verb+resource ('查询指定实例' = query the specified instance), which is clear, but it largely restates the tool name ShowInstance and adds no detail about what kind of instance data is returned. It does not distinguish itself from siblings such as ListInstances or ShowInstanceNodes beyond the implicit 'single instance' framing.

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 ListInstances over this tool, and no prerequisites. The only usage signal is the parenthetical '只读查询', which describes safety rather than selection criteria.

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