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

ListConfigHistories

ListConfigHistories
Read-onlyIdempotent

Retrieves parameter modification history for a specified cloud Redis instance, enabling paginated read-only configuration audits via limit and offset.

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

Input Schema

NameRequiredDescriptionDefault
limitNo每页显示条数,最小值为1,最大值为1000,若不设置该参数,则为10。
offsetNo偏移量,表示从此偏移量开始查询, offset大于等于0
regionNoOverrides HUAWEI_REGION.
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?

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description's '只读查询' merely restates what is already structured. It adds nothing about result volume, pagination limits, or what ordering records return in. For a read-only list endpoint, this is a thin layer of extra context.

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, front-loaded sentence with no filler. Its only minor defect is the redundant parenthetical restating the read-only annotation, which does not earn its place.

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?

The schema is fully documented and there is no output schema, so an agent can invoke the tool correctly. Still, for a five-parameter list tool, the description omits any mention of pagination results or record content, leaving the agent to rely entirely on structured fields.

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 five parameters, including limit, offset, region and project_id, are already documented in the schema's own descriptions. The tool description adds no meaning about parameter interaction, such as how offset and limit combine, or about required instance_id. A baseline 3 is correct when the schema carries the full 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 names a specific verb and resource in stating that it queries the list of instance parameter modification records ('查询实例参数修改记录列表'). This makes it distinguishable from the detail sibling, ShowConfigHistoryDetail, because it returns a list. However, it names no sibling explicitly, so it loses the final point.

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 only usage signal is the parenthetical '(只读查询)', which describes the operation's nature rather than when to call it. There is no guidance on when to use this list tool instead of ShowConfigHistoryDetail, nor on pagination strategy or which instance IDs are valid. An agent must infer the intended context.

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