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

ListBackgroundTask

ListBackgroundTask
Read-onlyIdempotent

Query the background task list for a cloud Redis instance to monitor or troubleshoot ongoing operations. Supports time range and pagination filters.

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

Input Schema

NameRequiredDescriptionDefault
limitNo每页显示的条目数量。
offsetNo偏移量,表示从此偏移量开始查询, offset大于等于0
regionNoOverrides HUAWEI_REGION.
end_timeNo查询结束时间,时间为UTC时间。格式:yyyyMMddHHmmss,如:20200617155959。
project_idNoOverrides HUAWEI_PROJECT_ID.
start_timeNo查询开始时间,时间为UTC时间。格式:yyyyMMddHHmmss,如:20200609160000。
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 '(只读查询)' parenthetical merely repeats structured data. Nothing is added about pagination defaults, time-range filtering behavior, result ordering, or what happens with large result sets.

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?

One short, unambiguous clause with zero padding and the read-only nature front-loaded. It is efficient, though the brevity borders on under-specification for a seven-parameter tool.

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 tool with seven parameters, region/project override semantics, and UTC time-range filtering — and with no output schema to describe return values — the description leaves too much unstated. It does not explain what a background task record contains or how pagination interacts with the time filters.

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 seven parameters including limit, offset, region, project_id, and the UTC time-range fields are already documented in the schema. The description contributes no additional meaning, which is the expected baseline when the schema carries the full parameter 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 states a specific verb and resource (query the background task list) and flags it as read-only, so an agent knows the operation type. It does not differentiate from sibling listing tools such as ListDiagnosisTasks, leaving selection between them 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 guidance on when to call this versus related tools like ShowBackgroundTaskProgress or the various List*Task tools, and no stated preconditions beyond the required instance_id in the schema. The agent must decide the routing itself.

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