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

ListMonitoredObjectsOfInstance

ListMonitoredObjectsOfInstance
Read-onlyIdempotent

Retrieve the monitored sub-dimension objects under a primary dimension for a DCS instance to identify which metrics can be queried during read-only troubleshooting.

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>",
      "dim_name": "<dim_name>"
    },
    "name": "ListMonitoredObjectsOfInstance"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
dim_nameYes主维度ID,当前支持子维度的主维度ID的有dcs_instance_id。
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes主维度对象ID,与DCS实例列表中实例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, openWorldHint=true, and destructiveHint=false, so restating "只读查询" adds no new information. The description says nothing about the scope of the returned list, whether results are paginated or bounded, or how a missing/invalid dim_name behaves.

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, front-loaded with the resource being listed and followed by the read-only qualifier. Nothing is wasted, though the terseness comes partly from omitted information rather than tight writing.

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 monitoring query with no output schema, the description never indicates what a returned object looks like or what dimension set is covered, and it leaves the relationship to the similarly named ListMonitoredObjects unresolved. The schema and annotations carry most of the load, but the description is too thin to disambiguate the tool set.

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%, and the schema itself explains instance_id (主维度对象ID), dim_name (currently only dcs_instance_id), and the region/project_id overrides, which is more than the description conveys. The description only gestures at "主维度" without adding format, valid values, or defaults, 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?

"查询单个主维度下子维度监控对象列表" gives a specific verb (query/list) and a specific resource (sub-dimension monitored objects under one main dimension), so an agent knows what it returns. It does not, however, distinguish this from the sibling ListMonitoredObjects, leaving the agent to guess which list tool applies.

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 usage signal is the parenthetical "只读查询", which tells the agent it is safe but not when to choose this over ListMonitoredObjects or any of the other List* siblings. There is no prerequisite, no exclusion, and no alternative named.

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