ncloud-mcp-server

ncloud_ses_create_cluster_g3

Create a Search Engine Service cluster on 3rd-generation KVM servers. Use dryRun=true to validate settings without creating resources.

Instructions

Create a new Search Engine Service cluster on 3rd-generation KVM servers (G3). Use dryRun=true to preview.

Input Schema

TableJSON Schema

Name	Required	Description
`vpcNo`	Yes	VPC number (from ncloud_ses_get_vpc_list)
`dryRun`	No	If true, preview only without creating
`clusterName`	Yes	Cluster name (3-15 chars: lowercase letters, numbers, '-'; starts with a letter, ends with a letter or number)
`loginKeyName`	Yes	Authentication key name (from ncloud_ses_get_login_keys)
`dataNodeCount`	Yes	Number of data nodes (3-10, default: 3)
`isDualManager`	No	Manager node redundancy (default: true)
`generationCode`	Yes	Server generation code. G3 for 3rd generation
`hypervisorCode`	Yes	Hypervisor code. KVM for 3rd generation
`serverSpecCode`	No	Server spec code. Optional here, unlike the CDSS G3 create where it is required
`masterNodeCount`	No	Number of master nodes (3 or 5, default: 3). Required when isMasterOnlyNodeActivated=true
`dataNodeSubnetNo`	Yes	Data node subnet number
`masterNodeSubnetNo`	No	Master node subnet number. Required when isMasterOnlyNodeActivated=true
`dataNodeProductCode`	Yes	Data node server type code
`dataNodeStorageSize`	Yes	Data node storage in GB (100-16000, 10GB increments)
`managerNodeSubnetNo`	Yes	Manager node subnet number (from ncloud_ses_get_subnet_list_g3)
`softwareProductCode`	Yes	G3 OS image code (see ncloud_ses_get_cluster_server_images; e.g. SW.VELST.OS.LNX64.ROCKY.08.G003)
`searchEngineUserName`	Yes	Admin account ID (3-15 chars: lowercase letters, numbers, '-')
`masterNodeProductCode`	No	Master node server type code. Required when isMasterOnlyNodeActivated=true
`managerNodeProductCode`	Yes	Manager node server type code (from ncloud_ses_get_server_specs)
`searchEngineVersionCode`	Yes	Search engine version code (from ncloud_ses_get_versions)
`searchEngineUserPassword`	Yes	Admin password (8-20 chars, letters+numbers+special; excludes ' " ` ₩ / & and spaces)
`isMasterOnlyNodeActivated`	No	Enable dedicated master nodes. If true, the three masterNode* parameters below are required
`searchEngineDashboardPort`	Yes	Dashboard port (1025-65534; 9090, 9200 and 9300 are unavailable)
`dataNodeStorageInfraResourceDetailTypeCode`	No	Data node storage type code. Documented valid value: CB1

Schema Changelog

Changes observed during successful MCP inspections.

Changed30 schema fields changedv1.15.0Sep 20, 2026

changedInput schema / properties / clusterName / description

Previous value: -"Cluster name (3-15 chars, lowercase+numbers+'-')"New value: +"Cluster name (3-15 chars: lowercase letters, numbers, '-'; starts with a letter, ends with a letter or number)"

addedInput schema / properties / clusterName / maxLength
```
Added value: +15
```

changedInput schema / properties / dataNodeCount / description

Previous value: -"Number of data nodes (3-10)"New value: +"Number of data nodes (3-10, default: 3)"

addedInput schema / properties / dataNodeCount / maximum
```
Added value: +10
```
addedInput schema / properties / dataNodeCount / minimum
```
Added value: +3
```

addedInput schema / properties / dataNodeProductCode

Added value: +{
+  "description": "Data node server type code",
+  "type": "string"
+}

removedInput schema / properties / dataNodeServerSpecCode

Removed value: -{
-  "description": "Data node server spec code",
-  "type": "string"
-}

addedInput schema / properties / dataNodeStorageInfraResourceDetailTypeCode

Added value: +{
+  "description": "Data node storage type code. Documented valid value: CB1",
+  "type": "string"
+}

changedInput schema / properties / dataNodeStorageSize / description

Previous value: -"Data node storage size in GB (100-2000)"New value: +"Data node storage in GB (100-16000, 10GB increments)"

addedInput schema / properties / dataNodeStorageSize / maximum
```
Added value: +16000
```
addedInput schema / properties / dataNodeStorageSize / minimum
```
Added value: +100
```

addedInput schema / properties / generationCode

Added value: +{
+  "description": "Server generation code. G3 for 3rd generation",
+  "type": "string"
+}

addedInput schema / properties / hypervisorCode

Added value: +{
+  "description": "Hypervisor code. KVM for 3rd generation",
+  "type": "string"
+}

changedInput schema / properties / isMasterOnlyNodeActivated / description

Previous value: -"Enable dedicated master nodes"New value: +"Enable dedicated master nodes. If true, the three masterNode* parameters below are required"

changedInput schema / properties / loginKeyName / description

Previous value: -"Authentication key name"New value: +"Authentication key name (from ncloud_ses_get_login_keys)"

addedInput schema / properties / managerNodeProductCode

Added value: +{
+  "description": "Manager node server type code (from ncloud_ses_get_server_specs)",
+  "type": "string"
+}

removedInput schema / properties / managerNodeServerSpecCode

Removed value: -{
-  "description": "Manager node server spec code (from getServerSpecList)",
-  "type": "string"
-}

changedInput schema / properties / managerNodeSubnetNo / description

Previous value: -"Manager node subnet number"New value: +"Manager node subnet number (from ncloud_ses_get_subnet_list_g3)"

changedInput schema / properties / masterNodeCount / description

Previous value: -"Number of master nodes (3 or 5)"New value: +"Number of master nodes (3 or 5, default: 3). Required when isMasterOnlyNodeActivated=true"

addedInput schema / properties / masterNodeProductCode

Added value: +{
+  "description": "Master node server type code. Required when isMasterOnlyNodeActivated=true",
+  "type": "string"
+}

removedInput schema / properties / masterNodeServerSpecCode

Removed value: -{
-  "description": "Master node server spec code",
-  "type": "string"
-}

changedInput schema / properties / masterNodeSubnetNo / description

Previous value: -"Master node subnet"New value: +"Master node subnet number. Required when isMasterOnlyNodeActivated=true"

changedInput schema / properties / searchEngineDashboardPort / description

Previous value: -"Dashboard port (1025-65534, not 9090/9200/9300)"New value: +"Dashboard port (1025-65534; 9090, 9200 and 9300 are unavailable)"

changedInput schema / properties / searchEngineUserName / description

Previous value: -"Admin account ID (3-15 chars)"New value: +"Admin account ID (3-15 chars: lowercase letters, numbers, '-')"

changedInput schema / properties / searchEngineUserPassword / description

Previous value: -"Admin password (8-20 chars)"New value: +"Admin password (8-20 chars, letters+numbers+special; excludes ' \" ` ₩ / & and spaces)"

changedInput schema / properties / searchEngineVersionCode / description

Previous value: -"Search engine version code"New value: +"Search engine version code (from ncloud_ses_get_versions)"

addedInput schema / properties / serverSpecCode

Added value: +{
+  "description": "Server spec code. Optional here, unlike the CDSS G3 create where it is required",
+  "type": "string"
+}

changedInput schema / properties / softwareProductCode / description

Previous value: -"OS type code (from getClusterServerImageList)"New value: +"G3 OS image code (see ncloud_ses_get_cluster_server_images; e.g. SW.VELST.OS.LNX64.ROCKY.08.G003)"

changedInput schema / properties / vpcNo / description

Previous value: -"VPC number"New value: +"VPC number (from ncloud_ses_get_vpc_list)"

changedInput schema / required

Previous value: -[
-  "clusterName",
-  "searchEngineVersionCode",
-  "searchEngineDashboardPort",
-  "searchEngineUserName",
-  "searchEngineUserPassword",
-  "softwareProductCode",
-  "vpcNo",
-  "managerNodeSubnetNo",
-  "managerNodeServerSpecCode",
-  "dataNodeSubnetNo",
-  "dataNodeCount",
-  "dataNodeServerSpecCode",
-  "dataNodeStorageSize",
-  "loginKeyName"
-]New value: +[
+  "clusterName",
+  "searchEngineVersionCode",
+  "searchEngineDashboardPort",
+  "searchEngineUserName",
+  "searchEngineUserPassword",
+  "softwareProductCode",
+  "hypervisorCode",
+  "generationCode",
+  "vpcNo",
+  "managerNodeSubnetNo",
+  "managerNodeProductCode",
+  "dataNodeSubnetNo",
+  "dataNodeCount",
+  "dataNodeProductCode",
+  "dataNodeStorageSize",
+  "loginKeyName"
+]

First observedv1.10.1Jul 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description clearly states that a new cluster is created and adds a useful dryRun preview hint. However, with only destructiveHint=false in annotations, it does not disclose async provisioning behavior, potential costs, or how to monitor the operation. The description adds some context but not much behavioral depth.

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 two tight sentences with no filler. The primary action and resource are front-loaded, and the dryRun preview tip is a useful one-line addition.

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 schema richly documents all 24 parameters, including source tools for many values, so the tool is callable. However, this is a high-complexity create operation with no output schema and no mention of return values, async behavior, or post-create verification. The description is adequate but not complete for such a heavyweight operation.

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 has 100% parameter description coverage, so the description carries little parameter burden. Mentioning dryRun and G3 adds minimal value beyond the schema's existing descriptions. 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 uses a specific verb ('Create'), a clear resource ('Search Engine Service cluster'), and a clear scope ('3rd-generation KVM servers (G3)'). The G3 mention differentiates it from siblings like ncloud_ses_create_cluster and the CDSS cluster-creation tools.

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?

The description does not state when to use this tool versus alternatives such as the non-G3 ncloud_ses_create_cluster or related CDSS cluster tools. The only guidance it offers is 'Use dryRun=true to preview,' which is a parameter-level tip, not a tool-selection guideline.

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

Deploy Server

ncloud_ses_create_cluster_g3

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools