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

ShowHotkeyTaskDetails

ShowHotkeyTaskDetails
Read-onlyIdempotent

Queries read-only hot key analysis task details for a Huawei DCS Redis instance by instance ID and hotkey task ID.

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>",
      "hotkey_id": "<hotkey_id>"
    },
    "name": "ShowHotkeyTaskDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
hotkey_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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description's '只读查询' merely repeats readOnlyHint and adds no new behavioral context such as error behavior for a missing or in-progress task.

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?

A single short phrase with zero waste and the resource front-loaded, but it is terse to the point of under-specification rather than being efficiently informative.

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 should indicate what '详情' returns (e.g., hot key names, counts, time window) and whether the task must be completed first. For a detail-retrieval tool with four parameters, the definition leaves the agent guessing about the result 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 description coverage is 100%, with instance_id, hotkey_id, region and project_id all documented inline, so the baseline is 3. The description adds no meaning beyond the schema, but none is required here.

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?

States a specific verb (查询) and resource (热key分析详情), which distinguishes it from the list-style sibling ListHotKeyScanTasks and from ShowBigkeyScanTaskDetails. It does not explicitly name an alternative, but the 'details' framing makes the scope legible.

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 the parenthetical '只读查询', which restates the read-only nature rather than telling the agent when to pick this over ListHotKeyScanTasks or ShowBigkeyScanTaskDetails. No prerequisites (e.g., task must exist or be finished) are given.

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