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

ListDiagnosisTasks

ListDiagnosisTasks
Read-onlyIdempotent

Retrieve the diagnosis task history for a cloud Redis instance to review past health checks. Use instance ID and optional pagination parameters for 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>"
    },
    "name": "ListDiagnosisTasks"
  }
}

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

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the description's 只读查询 note is a restatement that earns little additional credit. Beyond what the annotations already state, it says nothing about pagination behavior, the fields a task record contains, or rate limits. With annotations carrying the safety profile, this is still adequate but thin.

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 wasted words. It is terse but earns its place and does not bury the purpose. It is slightly minimal, which pushes it just below a 5.

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?

For a simple read-only list operation with fully covered schema parameters and annotations that declare the safety profile, this is mostly sufficient. However, the description omits how pagination behaves and what a diagnosis task record contains, which would help an agent call and interpret results correctly.

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 the schema already documents all five parameters, including limit/offset pagination and the region/project_id overrides. The description adds no meaning beyond that, but the baseline of 3 is appropriate 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 gives a clear verb plus resource combination: 查询 (query) plus 实例诊断任务列表 (instance diagnosis task list). This is a specific object of a specific type, so it is distinguishable from siblings such as ListBigkeyScanTasks or ListHotKeyScanTasks. However, it does not explicitly name or contrast any alternative, so it does not reach the full sibling-differentiation level.

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?

No when-to-use or when-not-to-use guidance is offered, no prerequisites are stated, and no alternative is named. The only contextual hint is the implied scoping to a single instance via the required instance_id, which the description does not make explicit.

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