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

ListHotKeyScanTasks

ListHotKeyScanTasks
Read-onlyIdempotent

Retrieve hot key analysis tasks for a specified Redis instance to review scan status and pagination details.

Instructions

查询热key分析任务列表(只读查询)

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

Input Schema

NameRequiredDescriptionDefault
limitNo每页显示的条目数量。
offsetNo偏移量,表示从此偏移量开始查询, offset大于等于0
regionNoOverrides HUAWEI_REGION.
statusNo分析任务状态
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, openWorldHint=true, and destructiveHint=false. The description merely repeats the read-only nature and adds no behavioral detail beyond annotations, such as pagination behavior, result ordering, or filtering semantics.

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 phrase with zero wasted wording and front-loads the core purpose. It is perhaps too terse, but it is structurally efficient.

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?

For a six-parameter list tool with pagination and filtering parameters and no output schema, the description is too minimal. It does not explain pagination, filtering by status, or how results relate to other task-listing tools.

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 six parameters, including instance_id, limit, offset, status, region, and project_id, are already documented in the schema. The description adds no extra meaning, which meets the baseline for fully documented schemas.

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 hot key analysis task list. It is clear what the tool does, but it does not name or distinguish itself from siblings like ListBigkeyScanTasks or ShowHotkeyTaskDetails.

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 '只读查询' (read-only query), which implies safe read usage but gives no guidance on when to choose this tool over ShowHotkeyTaskDetails or other task-listing tools, and no exclusions or prerequisites are stated.

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