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

BatchShowNodesInformation

BatchShowNodesInformation
Read-onlyIdempotent

Batch-retrieve node information for cloud Redis instances, with pagination, to support read-only troubleshooting and inspection.

Instructions

批量查询实例节点信息(只读查询)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "BatchShowNodesInformation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo每页显示的条目数量,当前最大值为100。若不设置该参数,则为10。
offsetNo偏移量,表示从此偏移量开始查询,offset大于等于0。
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The parenthetical 只读查询 merely restates readOnlyHint and adds no new behavioral context such as scope of the query, result ordering, or consequences of large limits.

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 verb and resource, with no filler. It is efficient, though its brevity leaves little room for the routing guidance an agent would benefit from.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All four parameters are optional and fully documented in the schema, and annotations carry the safety profile, so the definition is minimally sufficient. It remains unclear what a returned node record contains and how 批量 differs operationally from the singular sibling, which matters for a query tool with no output schema.

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 limit, offset, region and project_id each documented in the schema (including the 100/10 default behavior for limit). The description adds no meaning beyond that, so the baseline of 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 states a specific verb and resource: 批量查询 (batch query) of 实例节点信息 (instance node information). The 批量 prefix distinguishes it from the singular sibling ShowNodesInformation, though it does so only implicitly through the wording rather than by naming the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 批量 signals this is for retrieving node information across multiple nodes or instances, in contrast to the singular ShowNodesInformation. There is no explicit statement of when to prefer this tool over that sibling, and no mention of prerequisites or exclusions.

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