ncloud-gov-mcp-server

ncloud_create_network_interface

Create a network interface in a specified subnet with access control groups. Use dryRun to preview without creating.

Instructions

Create a new network interface. Use dryRun=true to preview.

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": {
      "subnetNo": "<subnetNo>",
      "accessControlGroupNoList": "<accessControlGroupNoList>"
    },
    "name": "ncloud_create_network_interface"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, returns a preview without actually creating
`subnetNo`	Yes	Subnet number to create the network interface in
`privateIp`	No	Private IP address to assign
`networkInterfaceName`	No	Network interface name
`accessControlGroupNoList`	Yes	List of ACG numbers to apply
`networkInterfaceDescription`	No	Network interface description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The annotation destructiveHint=false is supplemented by the description's mention of dryRun=true for previewing, which adds useful behavioral context. However, the description does not disclose other behaviors such as side effects, potential failures, or the async nature of creation, leaving some burden unmet.

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 exceptionally concise—two short sentences that state the action and the key preview option. There is zero redundant information, and the most important detail (creation) is front-loaded.

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 description is minimal but the schema is rich, covering all parameters. However, it lacks context about when to use this tool in a broader workflow (e.g., required resources like VPC/Subnet), how it relates to other NIC operations, or what to expect after creation, making it only moderately complete.

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 every parameter already having a clear description. The tool description adds no additional parameter-level meaning beyond what the schema provides, so it stays at the baseline of 3.

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 action ('Create a new network interface') with a specific verb and resource. It is distinct from sibling tools like delete_network_interface, list_network_interfaces, and attach_network_interface, making the purpose unambiguous.

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 through the verb 'Create', but does not explicitly state when to use this tool versus alternatives or any prerequisites. The only guidance is the dryRun hint, which is a preview feature but not a full usage guideline.

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

Deploy Server