ncloud-gov-mcp-server

ncloud_attach_network_interface

Idempotent

Attach a network interface to a server instance by providing the network interface number and server instance number. Connects the interface to enable network configuration.

Instructions

Attach a network interface to a server instance

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": {
      "networkInterfaceNo": "<networkInterfaceNo>",
      "serverInstanceNo": "<serverInstanceNo>"
    },
    "name": "ncloud_attach_network_interface"
  }
}

Input Schema

Name	Required	Description	Default
`serverInstanceNo`	Yes	Server instance number to attach to
`networkInterfaceNo`	Yes	Network interface number to attach

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, so the agent knows the operation is safe and repeatable. However, the description adds no extra behavioral context such as prerequisites, side effects, or state changes beyond the literal action, and does not mention anything about server/interface states.

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?

One concise sentence with no redundancy or filler; clearly front-loaded with the action. Every word earns its place.

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?

Given the simple two-parameter operation, the schema provides complete parameter descriptions, and annotations cover safety traits. However, the description omits usage context and behavioral nuances such as whether the network interface must be detached first or if the server must be in a specific state, leaving the overall context slightly incomplete.

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 covers both parameters with clear descriptions, and the description aligns with them. No additional parameter details are needed beyond what the schema already provides.

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 uses a specific action verb 'Attach' with a clear resource 'network interface' and target 'server instance', making it distinct from sibling operations like detach_network_interface, create_network_interface, and add_nic_acg. It fully identifies what the tool does.

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 such as ncloud_detach_network_interface or ncloud_create_network_interface. The description simply states the operation without context on prerequisites, state requirements, or alternative actions.

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

Deploy Server