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

ListBigkeyScanTasks

ListBigkeyScanTasks
Read-onlyIdempotent

Retrieves paginated big key analysis tasks for a specified Redis instance, so you can review scan status and results in read-only mode.

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

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.8/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, and the description adds nothing beyond the '只读查询' restatement. It does not explain result ordering, pagination behavior, or what happens with an invalid status filter, so no behavioral value is added on top of structured fields.

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?

The single short phrase is front-loaded and free of waste, but it is under-specified rather than genuinely concise, with the parenthetical adding redundant information. No structural elements such as scope or routing guidance are present.

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?

With six parameters, a required instance_id, and no output schema, the description should at least clarify return contents or pagination expectations. Instead it offers only a one-line restatement, leaving an agent to infer how results are ordered and how limit/offset interact.

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 every parameter including limit, offset, status, region and project_id is already documented in the schema. The description contributes no additional meaning about these parameters, which matches the baseline of 3 when the schema does the heavy lifting.

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 (大key分析任务列表), which separates it from siblings like ShowBigkeyScanTaskDetails and ListHotKeyScanTasks by resource and scope. It is clear but does not explicitly name any sibling or contrast its scope.

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 guidance is '(只读查询)', which restates the readOnlyHint annotation rather than telling the agent when to choose this list tool over the detail tool or the hot-key variant. There is no mention of pagination, filtering by status, or prerequisites such as instance_id.

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