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

ListMonitoredObjects

ListMonitoredObjects
Read-onlyIdempotent

Retrieve monitored object lists by main dimension ID (e.g., DCS instance IDs) with pagination for read-only troubleshooting and inventory checks.

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

Input Schema

NameRequiredDescriptionDefault
limitNo每页显示的条目数量
offsetNo偏移量,表示从此偏移量开始查询,offset大于等于0
regionNoOverrides HUAWEI_REGION.
dim_nameYes主维度ID,当前支持dcs_instance_id,dcs_memcached_instance_id。
project_idNoOverrides HUAWEI_PROJECT_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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, and destructiveHint=false, so the '(只读查询)' parenthetical merely repeats structured data and earns no credit. With that low bar the description still adds nothing new: no return-shape hint, no statement about pagination limits on the offset/limit pair, and no note that region/project_id override environment defaults. This is repetition rather than disclosure.

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?

The definition is a single short, front-loaded sentence with no filler paragraphs. It loses some credit because the only elaboration it offers, the read-only parenthetical, duplicates the annotations and thus does not earn its place, while genuinely useful detail is omitted.

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 five-parameter list tool with no output schema and a near-duplicate sibling, the description should at minimum explain what a 'main dimension' record is and when to prefer the OfInstance variant. Neither is present, leaving the agent to infer the tool's role from its name. The rich schema partly compensates, but not enough to make the definition self-sufficient.

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 five parameters (limit, offset, region, dim_name, project_id) are already documented in the schema, including the supported dim_name values. The description adds no semantic meaning beyond that, so the baseline of 3 applies. It misses an opportunity to explain that dim_name selects which monitored-object family is returned.

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?

The description states a verb (查询/query) and a resource (主维度信息列表/monitored-object dimension list), so the basic operation is identifiable. However, '主维度' is unexplained domain jargon and the description does nothing to distinguish this tool from the near-identical sibling ListMonitoredObjectsOfInstance. An agent cannot tell from the text alone which of the two list endpoints it wants.

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 when-to-use guidance, no prerequisites, and no named alternative. The only hint is the parenthetical '(只读查询)', which is a safety restatement rather than a usage condition. Contrast with a strong definition that would say to use this for the catalog of dimensions and ListMonitoredObjectsOfInstance for a specific instance.

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