Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_network_interface

Create a new network interface in a VPC subnet by specifying the VPC, subnet, and 1-3 access control groups; set dryRun to preview before creation.

Instructions

Create a new network interface in a VPC subnet. vpcNo, subnetNo and 1-3 ACG numbers are required. Use dryRun=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoPrimary private IP within the subnet range (auto-assigned when omitted; the first 6 and the last subnet addresses are reserved)
vpcNoYesVPC number the subnet belongs to (required; see ncloud_list_vpcs)
dryRunNoIf true, returns a preview without actually creating
subnetNoYesSubnet number to create the network interface in (required)
isBareMetalNotrue for a bare-metal server interface (requires serverInstanceNo)
secondaryIpListNoSecondary IPs to assign (together with secondaryIpCount at most 5)
secondaryIpCountNoNumber of secondary IPs to auto-assign (0-5)
serverInstanceNoNoServer instance to attach to on creation (private-subnet interfaces only)
networkInterfaceNameNoNetwork interface name (3-30 chars: lowercase letters, digits, '-'; auto-generated when omitted)
accessControlGroupNoListYesList of ACG numbers to apply (1-3)
networkInterfaceDescriptionNoNetwork interface description (up to 1000 bytes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv2.0.1
    • changedInput schema / properties / accessControlGroupNoList / description
      Previous value: -"List of ACG numbers to apply"New value: +"List of ACG numbers to apply (1-3)"
    • addedInput schema / properties / accessControlGroupNoList / maxItems
      Added value: +3
    • addedInput schema / properties / ip
      Added value: +{
+  "description": "Primary private IP within the subnet range (auto-assigned when omitted; the first 6 and the last subnet addresses are reserved)",
+  "type": "string"
+}
    • addedInput schema / properties / isBareMetal
      Added value: +{
+  "description": "true for a bare-metal server interface (requires serverInstanceNo)",
+  "type": "boolean"
+}
    • changedInput schema / properties / networkInterfaceDescription / description
      Previous value: -"Network interface description"New value: +"Network interface description (up to 1000 bytes)"
    • changedInput schema / properties / networkInterfaceName / description
      Previous value: -"Network interface name"New value: +"Network interface name (3-30 chars: lowercase letters, digits, '-'; auto-generated when omitted)"
    • removedInput schema / properties / privateIp
      Removed value: -{
-  "description": "Private IP address to assign",
-  "type": "string"
-}
    • addedInput schema / properties / secondaryIpCount
      Added value: +{
+  "description": "Number of secondary IPs to auto-assign (0-5)",
+  "maximum": 5,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / secondaryIpList
      Added value: +{
+  "description": "Secondary IPs to assign (together with secondaryIpCount at most 5)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / serverInstanceNo
      Added value: +{
+  "description": "Server instance to attach to on creation (private-subnet interfaces only)",
+  "type": "string"
+}
    • changedInput schema / properties / subnetNo / description
      Previous value: -"Subnet number to create the network interface in"New value: +"Subnet number to create the network interface in (required)"
    • addedInput schema / properties / vpcNo
      Added value: +{
+  "description": "VPC number the subnet belongs to (required; see ncloud_list_vpcs)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "subnetNo",
-  "accessControlGroupNoList"
-]New value: +[
+  "vpcNo",
+  "subnetNo",
+  "accessControlGroupNoList"
+]
  2. First observedv1.10.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description carries most of the behavioral burden. It notes the dryRun preview path, which is useful, but it doesn't disclose permissions needed, whether the NIC is created unattached, or reversibility — and the dryRun detail is already restated in the schema.

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?

Two sentences, front-loaded with the action, then requirements, then the preview hint. Nothing is padded and no sentence is redundant.

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 an 11-parameter create operation with only a single annotation and no output schema, the description is minimal. It covers required inputs and preview mode, but omits return/response context and any lifecycle or attachment behavior an agent might need when invoking a creation tool.

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%, so all 11 parameters are already documented in the schema. The description only restates the three required fields and dryRun, adding no syntax, constraints, or edge-case meaning beyond what the schema provides; baseline 3 is appropriate.

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 gives a specific verb ('Create'), a specific resource ('network interface'), and the scope ('in a VPC subnet'), which cleanly separates it from the sibling list/get/delete/attach/detach NIC operations. An agent can identify the action without opening the schema.

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?

It states the required inputs and offers one usage tip ('Use dryRun=true to preview'), which is helpful. However, it never says when this is the right tool versus alternatives (e.g. attaching an existing NIC vs creating one) or any prerequisites such as server-attachment context.

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