ncloud-gov-mcp-server

ncloud_nks_add_subnet

Add subnets to an NKS cluster by providing the cluster UUID and a list of subnet numbers to expand network capacity.

Instructions

Add subnets to an NKS cluster

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": {
      "clusterUuid": "<clusterUuid>",
      "subnetNoList": "<subnetNoList>"
    },
    "name": "ncloud_nks_add_subnet"
  }
}

Input Schema

Name	Required	Description	Default
`clusterUuid`	Yes	UUID of the cluster
`subnetNoList`	Yes	List of subnet numbers to add

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations provide only destructiveHint=false, which is minimal. The description adds no behavioral context beyond the action itself, such as whether subnets are added incrementally, if there are any side effects, or if the operation is reversible. For a mutating operation, this is a significant gap.

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, focused sentence with no redundancy. Every word contributes to the meaning, and the structure is clean and front-loaded with the action.

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

Completeness2/5

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

For a mutation with no output schema and minimal annotations, the description does not provide adequate context. It omits any information about return values, idempotency, associated costs, or the relationship to cluster networking, leaving the agent with limited understanding of the operation's full implications.

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 already describes both parameters (clusterUuid and subnetNoList) with clear descriptions, covering 100% of the schema. The description adds no additional parameter-level detail, so the baseline of 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 'Add subnets to an NKS cluster' uses a specific verb and resource, clearly indicating what the tool does. It differentiates from sibling tools like ncloud_nks_update_node_pool_subnet or ncloud_nks_create_cluster because it specifically targets adding subnets at the cluster level.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives, nor does it state any prerequisites or conditions. The one-sentence description is purely functional and lacks context for selection.

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

Deploy Server