Skip to main content
Glama
Huawei DCS MCP
by key-well

ShowConfigHistoryDetail

ShowConfigHistoryDetail
Read-onlyIdempotent

Retrieve details for a specific configuration parameter modification record by instance ID and history ID to support read-only 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>",
      "history_id": "<history_id>"
    },
    "name": "ShowConfigHistoryDetail"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
history_idYes历史实例ID
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes实例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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the description's '(只读查询)' merely restates structured data. It adds no behavioral context such as what a history detail entry contains, whether records can expire, or any throttling or 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 no wasted words and is front-loaded, but at this length conciseness shades into under-specification rather than efficiency. The duplicated read-only note is the only clause beyond the noun phrase.

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 read-only detail lookup with full schema coverage and annotations covering the safety profile, little more is strictly required to call it correctly. The remaining gap is that with no output schema, the description never hints at what a 'record detail' returns.

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 all four parameters, including the region/project_id overrides, are already documented in the schema. The description contributes no additional meaning about how history_id relates to instance_id or where history_id comes from; baseline 3 applies.

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+resource: querying the detail of an instance parameter modification record, which is more precise than the bare tool name. It does not, however, distinguish itself from the sibling ListConfigHistories, leaving the list-vs-detail distinction to inference.

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 statement of when to use this tool versus ListConfigHistories or any other sibling; the parenthetical only labels it a read-only query. No prerequisites (e.g., needing an instance_id plus a history_id obtained from the list tool) are mentioned.

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