Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_set_subnet_network_acl

Idempotent

Assign a Network ACL to a subnet to control traffic by specifying the subnet and Network ACL numbers.

Instructions

Set the Network ACL for a subnet

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

Input Schema

NameRequiredDescriptionDefault
subnetNoYesSubnet number to assign the Network ACL to
networkAclNoYesNetwork ACL number to assign

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/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, so the agent knows this is a safe, repeatable operation. The description adds no additional behavioral context, such as whether an existing ACL association is replaced or any side effects, but does not contradict the annotations.

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, front-loaded sentence that conveys the core purpose with zero wasted words. It is appropriately sized for the tool's simplicity.

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 two-parameter tool with full schema coverage and safety annotations, the description is minimally adequate. However, it lacks context about behavior when a subnet already has an ACL or whether the network ACL must exist, leaving some gaps for a complex cloud environment.

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 input schema covers both parameters with descriptions (100% coverage), so the baseline is 3. The description does not add extra meaning beyond the schema; it only implies the parameters from the phrase 'for a subnet' and 'Network ACL'.

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 'Set the Network ACL for a subnet' clearly states the action (set) and the resource (Network ACL for a subnet). It is specific enough to distinguish from sibling tools like set_network_acl_description, though it does not explicitly mention that it assigns an existing ACL to a subnet.

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. There are no mentions of prerequisites, valid scenarios, or exclusions, which is a clear gap given the large set of sibling tools.

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

Deploy Server

Other Tools