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

ShowDiagnosisTaskDetails

ShowDiagnosisTaskDetails
Read-onlyIdempotent

Retrieves the details of a specified diagnosis report by report ID for a cloud Redis instance, enabling read-only troubleshooting without modifying resources.

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": {
      "report_id": "<report_id>"
    },
    "name": "ShowDiagnosisTaskDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
report_idYes诊断报告ID
project_idNoOverrides HUAWEI_PROJECT_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 the parenthetical "(只读查询)" merely repeats that read-only claim without adding context. Nothing is said about whether a missing report errors, what authentication/region resolution applies, or how complete the report payload is, so the description contributes no behavior beyond structured fields.

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 phrase with no wasted words, so nothing needs trimming. However, it is under-specified rather than concise: the one sentence carries almost no information load and the parenthetical adds a redundant qualifier instead of useful detail.

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 low-complexity read tool with full schema coverage and a rich annotation set, the minimum bar is still to say how it relates to ListDiagnosisTasks and what the returned report represents. With no output schema and no description of results or the meaning of a 'diagnosis report', the definition leaves the agent guessing about selection and expectations.

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 three parameters (report_id, region, project_id) are already documented in the schema, which sets the baseline at 3. The description offers no additional meaning about the ID format or override precedence, but none is strictly required given full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"查询指定诊断报告" gives a verb (query) and a resource (diagnosis report), and "指定" implies retrieval of a single report by ID, which loosely separates it from ListDiagnosisTasks. But the phrase largely restates the tool name (Show...Details) and never states what a 'diagnosis report' contains or how it differs from a diagnosis task, so the purpose is only minimally clearer than the name 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?

There is no guidance on when to call this versus the sibling ListDiagnosisTasks, nor on where the required report_id comes from. No prerequisites, no exclusions, and no mention of when the region/project_id overrides should be supplied — the agent must infer all usage conditions.

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