ncloud-mcp-server

ncloud_list_deny_allow_groups

Read-only

List Network ACL Deny-Allow Groups by VPC, name, or group number to review and manage access control rules.

Instructions

List Network ACL Deny-Allow Groups

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": "ncloud_list_deny_allow_groups"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	No	Filter by VPC number
`networkAclDenyAllowGroupName`	No	Filter by Deny-Allow Group name
`networkAclDenyAllowGroupNoList`	No	Filter by Deny-Allow Group numbers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint annotation already declares this as a safe read operation, and the description does not contradict this. However, it adds no additional behavioral context such as pagination, result size limits, or whether the group numbers filter returns a list. The description carries minimal burden beyond the annotation, consistent with the midpoint on the scale.

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?

The description is a single, clear sentence with no filler. It effectively conveys the tool's purpose in the fewest words possible, earning a perfect score for conciseness.

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

Completeness4/5

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

Given the tool's simplicity (no output schema, three optional filter parameters), the description is adequately complete. It names the resource and action, and the schema covers parameters. It lacks domain context about what a Deny-Allow Group is, but that is not strictly necessary for an agent to invoke the tool correctly.

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 each parameter (vpcNo, networkAclDenyAllowGroupName, networkAclDenyAllowGroupNoList) having its own description. The tool description adds no extra parameter semantics, but this is acceptable given the schema already provides full coverage. 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 'List Network ACL Deny-Allow Groups' uses a specific verb ('List') and resource ('Network ACL Deny-Allow Groups'), clearly distinguishing it from related sibling tools like ncloud_get_deny_allow_group_detail and ncloud_create_deny_allow_group. However, it does not explicitly state the scope (e.g., all groups or filtered) beyond what the schema implies.

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?

No guidance is provided on when to use this tool versus alternatives such as ncloud_get_deny_allow_group_detail or ncloud_list_network_acls. The description simply states what it does, leaving the agent to infer usage context from the name and schema.

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

Deploy Server