Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ncloud_nks_create_cluster

Create a new NKS Kubernetes cluster with dry-run preview. Supports G2/XEN and G3/KVM hypervisors, configurable node pools, subnets, and load balancers.

Instructions

Create a new NKS Kubernetes cluster. Use dryRun=true to preview without creating.

G3(KVM) cluster requirements:

  • hypervisorCode: 'KVM' (required)

  • clusterType: must contain G003 (e.g., SVR.VNKS.STAND.C004.M016.G003)

  • k8sVersion: must use nks.2 suffix (e.g., 1.35.3-nks.2)

  • lbPrivateSubnetNo: Private LB subnet number (required — returns 400 without details if missing)

  • zoneCode: Required at cluster level when isRegional=false (default). Missing causes 400 without details.

  • nodePool.softwareCode: Must use FULL value from ncloud_nks_get_server_images including pipe and image number (e.g., SW.VSVR.OS.LNX64.UBNTU.SVR22.WRKND.G003|23215604)

  • nodePool.serverSpecCode: g3 spec code (e.g., c2-g3)

  • nodePool.storageSize: 100~2000GB (required)

G2(XEN) vs G3(KVM) differences:

  • G2: clusterType contains G002, k8sVersion suffix nks.1, hypervisorCode optional

  • G3: clusterType contains G003, k8sVersion suffix nks.2, hypervisorCode='KVM' required

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logNoLog settings (audit log)
nameYesCluster name (3-30 chars, lowercase+numbers+'-')
vpcNoYesVPC number
dryRunNoIf true, returns a preview without actually creating
nodePoolNoInitial node pool configurations
zoneCodeNoZone code (e.g., KR-2). Required when isRegional is false (default). API returns 400 without details if missing for single-zone clusters
isRegionalNoMulti-zone (Regional) cluster. Default: false
k8sVersionNoKubernetes version (from ncloud_nks_get_versions). G3/KVM uses nks.2 suffix, G2/XEN uses nks.1 suffix
regionCodeYesRegion code (e.g., KR, SGN, JPN)
clusterTypeYesCluster type (e.g., SVR.VNKS.STAND.C004.M016.G003 for G3, SVR.VNKS.STAND.C004.M016.G002 for G2)
loginKeyNameYesLogin key name for node access
subnetNoListYesSubnet number list for the cluster
publicNetworkNoSubnet network type. true=Public, false=Private (default)
hypervisorCodeNoHypervisor code: XEN (default) or KVM. Required as 'KVM' for G3 clusters
lbPublicSubnetNoYesLoad balancer public subnet number
lbPrivateSubnetNoNoLoad balancer private subnet number. Required for G3/KVM clusters (API returns 400 without details if missing)

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations include only destructiveHint=false, which is brief. The description adds significant behavioral context: the dryRun preview, error behavior for missing parameters (returns 400 without details), required fields for G3, and constraints like storage size range. This far exceeds the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with clear sections for G3 requirements and G2 vs G3 differences. It front-loads the main action and dryRun. However, some information could be more concise; the schema already documents many constraints, so the description repeats some of that.

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

Completeness5/5

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

Given the tool's complexity (16 parameters, nested objects, no output schema), the description covers all essential aspects: creation action, preview mode, hypervisor-specific requirements, error behavior, and parameter constraints. An AI agent can correctly invoke this tool based on the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, baseline is 3. However, the description adds crucial context beyond schema: for example, it explains that hypervisorCode must be 'KVM' for G3, clusterType must contain G003, k8sVersion suffix, the full format for softwareCode, and which parameters are required for G3 vs G2. This adds immense value.

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 'Create a new NKS Kubernetes cluster,' which is a specific verb+resource. It also mentions dryRun for preview. Among sibling tools like ncloud_nks_list_clusters or ncloud_nks_delete_cluster, this is the only creation tool, making it easily distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use G3 vs G2 clusters, with detailed requirements for each hypervisor. It also explains when dryRun can be used for preview. The G3 vs G2 comparison helps the agent choose the correct configuration.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server