Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_create_server

Create a new server instance on Naver Cloud Platform. Supports KVM (Gen3) and XEN (Gen2) with configurable volumes, networks, and a dry-run preview option.

Instructions

Create a new server instance. For KVM (Gen3): use serverImageNo + serverSpecCode; for the boot volume (blockStorageMappingList order 0), prefer CB2 unless the user asks otherwise — CB2 is the recommended default for Gen3 KVM (volume type cannot be changed after creation). For XEN (Gen2): use serverImageProductCode + serverProductCode, or serverImageNo + serverSpecCode. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpcNoYesVPC number
dryRunNoIf true, returns a preview without actually creating the server
subnetNoYesSubnet number
serverNameNoServer name (lowercase+numbers+hyphen, 3-30 chars)
initScriptNoNoInit script number
loginKeyNameNoLogin key name for SSH access
serverImageNoNoServer image number from ncloud_get_server_images (required for KVM/Gen3)
serverSpecCodeNoServer spec code from ncloud_get_server_specs (required for KVM/Gen3, e.g., c2-g3, s2-g3)
placementGroupNoNoPlacement group number
feeSystemTypeCodeNoFee system type (MTRAT: hourly, FXSUM: monthly)
serverDescriptionNoServer description
serverProductCodeNoServer product code (legacy, XEN/RHV only, use with serverImageProductCode)
networkInterfaceListNoNetwork interface configuration list
associateWithPublicIpNoAssociate a new public IP on creation
serverImageProductCodeNoServer image product code (legacy, XEN/RHV only)
blockStorageMappingListNoBlock storage mapping — KVM (Gen3) only. Selects the boot volume type (order 0) and/or creates additional volumes at server creation. Recommendation: for a KVM boot volume set order 0 + blockStorageVolumeTypeCode 'CB2' unless the user asks otherwise. If omitted entirely, the API default (CB1) is used. Not supported on XEN (Gen2).
isProtectServerTerminationNoEnable termination protection
memberServerImageInstanceNoNoMember server image instance number (custom image)
Behavior4/5

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

The description adds behavioral details beyond the annotations (destructiveHint: false): volume type cannot be changed after creation, dryRun preview behavior, and the recommendation for CB2. No contradiction with annotations.

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 concise, well-structured, and front-loaded with the core purpose. Every sentence provides essential information without redundancy.

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

Completeness4/5

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

Given the complex parameter interactions (18 parameters), the description provides sufficient guidance for the critical choices (gen-specific parameters, volume type recommendation, dryRun). No output schema exists, but the description doesn't need to explain return values as the tool's output is straightforward.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds significant meaning by grouping parameters for KVM vs XEN, explaining the blockStorageMappingList usage for boot volumes, and recommending defaults. This adds value beyond the schema's individual property descriptions.

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 the tool's purpose ('Create a new server instance') and immediately distinguishes between KVM (Gen3) and XEN (Gen2) server types, specifying which parameters to use for each. This differentiates it from sibling tools like ncloud_terminate_server, ncloud_list_servers, etc.

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

Usage Guidelines4/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 serverImageNo+serverSpecCode vs serverImageProductCode+serverProductCode based on the generation, recommends CB2 for KVM boot volumes, and suggests using dryRun=true for preview. It does not explicitly state when not to use this tool, but the context is clear.

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