ncloud-gov-mcp-server

ncloud_set_network_acl_description

Idempotent

Set or update the description of a Network ACL using its network ACL number and new description text. Modify network access control list details for better management.

Instructions

Set or update the description of a Network ACL

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": {
      "networkAclNo": "<networkAclNo>",
      "networkAclDescription": "<networkAclDescription>"
    },
    "name": "ncloud_set_network_acl_description"
  }
}

Input Schema

Name	Required	Description	Default
`networkAclNo`	Yes	Network ACL number
`networkAclDescription`	Yes	New description for the Network ACL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context beyond the simple 'set or update' action, such as effects on existing rules or whether the description is required to be non-empty. It does not contradict annotations, but provides no additional transparency.

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, concise sentence that is front-loaded with the action and resource. Every word earns its place, with zero redundancy or filler.

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

Completeness5/5

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

For a simple update tool with only 2 documented parameters, no output schema, and annotations covering idempotency and destructiveness, the description is fully sufficient. The tool's purpose and required inputs are unambiguous, and no additional context is necessary for correct invocation.

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%, and both parameters are clearly documented ('Network ACL number' and 'New description'). The description adds no extra meaning beyond the schema, but this is acceptable given the high coverage. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Set or update') and the resource ('Network ACL description'), making the tool's purpose unambiguous. It distinguishes from sibling tools like ncloud_get_network_acl_detail or ncloud_delete_network_acl by specifying exactly what it modifies.

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?

The description implies usage for modifying an existing Network ACL's description, but provides no explicit guidance on when to prefer this tool over alternatives (e.g., using ncloud_set_subnet_network_acl for subnet association, or ncloud_create_network_acl for new ACLs). There are no exclusions or alternative recommendations, but the context is clear enough for basic selection.

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

Deploy Server