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

ShowBigkeyScanTaskDetails

ShowBigkeyScanTaskDetails
Read-onlyIdempotent

Retrieves read-only details for a Redis big-key analysis task by instance ID and task ID, helping inspect large-key scan results.

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>",
      "bigkey_id": "<bigkey_id>"
    },
    "name": "ShowBigkeyScanTaskDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
bigkey_idYes大key分析任务ID。
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so restating 只读查询 adds nothing beyond structured data. The description says nothing about what happens when bigkey_id is unknown, whether results are paginated, or what the task-detail payload contains.

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?

A single short sentence with the resource front-loaded and no filler. The parenthetical 只读查询 is slightly redundant given the annotations, but it costs almost nothing.

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?

There is no output schema, so the description carries the burden of saying what the returned analysis details are (e.g. key names, sizes, element counts) and whether the task must be finished. It supplies none of that, leaving the agent unable to anticipate the response shape.

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 coverage is 100% and both required parameters (instance_id, bigkey_id) plus the region/project_id overrides are documented in the schema itself. The description adds no meaning beyond that, so the baseline 3 applies.

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 names a specific verb (查询) and resource (大key分析详情), so an agent can tell it retrieves the details of one big-key analysis task rather than a list. It does not explicitly contrast with siblings such as ListBigkeyScanTasks or ShowHotkeyTaskDetails, so it stops short of a 5.

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 use this tool versus the list variant or the hotkey equivalent, and no stated preconditions such as the task having completed. The only hint is the parenthetical 只读查询, which is a safety note rather than usage guidance.

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