ncp-mcp-server

list_acgs

List Access Control Groups (ACGs) in Naver Cloud Platform. Optionally filter by VPC number to focus on a specific virtual network.

Instructions

ACG(Access Control Group) 목록을 조회합니다

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

Input Schema

Name	Required	Description	Default
`vpcNo`	No	VPC 번호 (선택사항)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 5, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description only says 'retrieve list' without disclosing read-only behavior, pagination, or any side effects. It also fails to mention that the vpcNo parameter filters results, which is important behavioral context.

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 wasted words. It is appropriately concise for a simple list operation and is easy to parse quickly.

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?

The tool is simple with one optional parameter, but there is no output schema, and the description does not explain the return value or any limitations. It is adequate but lacks details like whether a list of ACG objects or IDs is returned.

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 fully documents the single parameter vpcNo with 'VPC number (optional)', giving 100% coverage. The description adds no additional parameter meaning, so it does not exceed the baseline.

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 clearly states 'Retrieves the list of ACG (Access Control Group)', providing a specific verb and resource. However, it does not differentiate from sibling list tools like list_servers or list_vpcs, so it stops short of a full 5.

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 guidance on when to use this tool versus alternatives. It does not mention whether to use it before creating/deleting ACGs or how the optional vpcNo filter should be used, leaving usage entirely implied.

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