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

ShowBackgroundTaskProgress

ShowBackgroundTaskProgress
Read-onlyIdempotent

Retrieve read-only details and progress for a specific background task on a Huawei DCS Redis instance to monitor asynchronous operations.

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>",
      "task_id": "<task_id>"
    },
    "name": "ShowBackgroundTaskProgress"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
task_idYes任务ID。
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, destructiveHint=false and openWorldHint=true, and 只读查询 merely repeats the read-only fact with no added context. There is no mention of what fields come back, how a not-found or still-running task behaves, or that this hits a remote region endpoint despite openWorldHint=true.

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?

It is a single short clause with zero filler and the purpose is front-loaded, which is good. But at this length the brevity shades into under-specification, leaving too much for the agent to infer.

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 four-parameter tool with two required IDs and no output schema, the definition should say more: which kinds of background task exist, where the IDs come from, and how this differs from the many sibling Show*/List* task tools. With rich annotations covering safety, the remaining gaps are mostly about discovery and routing, which are unaddressed.

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?

All four parameters are fully documented in the schema, including that region and project_id override HUAWEI_REGION and HUAWEI_PROJECT_ID, so the schema carries the load and the baseline of 3 applies. The description adds no meaning about how task_id relates to instance_id or whether the task must belong to the given instance.

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 pairs a specific verb (查询) with a specific resource (后台任务详细信息), so the agent knows this returns detail for a single background task. It does not, however, distinguish itself from the sibling ListBackgroundTask, leaving the detail-vs-list split to be inferred from names alone.

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 offered is the parenthetical 只读查询, which restates the read-only safety profile rather than explaining when to choose this tool. Nothing says to use it after obtaining a task ID from ListBackgroundTask, or when the instance_id/task_id pair is required versus when a list is sufficient.

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