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

ShowIpWhitelist

ShowIpWhitelist
Read-onlyIdempotent

Retrieve the IP whitelist for a specified cloud Redis instance to review which addresses are allowed to connect. Use this read-only query to verify access settings without changing resources.

Instructions

查询指定实例的IP白名单(只读查询)

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

Input Schema

NameRequiredDescriptionDefault
regionNoOverrides HUAWEI_REGION.
project_idNoOverrides HUAWEI_PROJECT_ID.
instance_idYes实例ID。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered. The description's parenthetical "(只读查询)" merely repeats readOnlyHint and adds nothing about authentication, per-region/per-project behavior, or what the whitelist response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the resource and scope up front and no padding. Nothing in it is wasted, even if more detail would have been useful elsewhere.

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?

For a simple read-only lookup with full schema coverage and rich annotations, the description is adequate but thin. It omits how the instance's whitelist is returned and whether results are paginated or grouped, which matters since no output schema exists.

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?

The schema description coverage is 100%, so instance_id, region, and project_id are already documented, including the HUAWEI_REGION/HUAWEI_PROJECT_ID override semantics. The description only echoes that the instance is required and adds no meaning beyond the schema, which meets the baseline-3 expectation.

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 gives a specific verb and resource in Chinese: query the IP whitelist of a specified instance. An agent can tell it is a per-instance whitelist read, though the description never contrasts it with sibling list/show tools such as ListInstances or ShowInstance.

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 by the resource name: an agent can infer you call this when you need to see which IPs are allowed on an instance. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named.

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