Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_launch_config

Create a launch configuration for Auto Scaling by specifying one image source (product code, image number, or member image) and a server spec code. Use dryRun to preview.

Instructions

Create a new launch configuration for Auto Scaling. Exactly one image source must be provided: serverImageProductCode, serverImageNo, or memberServerImageInstanceNo. A server spec is also required: serverImageProductCode → serverProductCode (XEN/RHV); serverImageNo / memberServerImageInstanceNo → serverSpecCode (KVM, see ncloud_get_server_specs). Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns a preview without actually creating
initScriptNoNoInit script number to run on first boot
loginKeyNameNoLogin key name for SSH access (defaults to the most recently created key)
serverImageNoNoServer image number — for a new (public) server image (required path for KVM/Gen3). One of serverImageProductCode / serverImageNo / memberServerImageInstanceNo is required.
serverSpecCodeNoServer spec code — pair with serverImageNo or memberServerImageInstanceNo (KVM/Gen3, e.g. c2-g3, s2-g3). One of serverProductCode / serverSpecCode is required (the API rejects a request without a spec).
isEncryptedVolumeNoWhether to encrypt the root volume (RHV only)
serverProductCodeNoServer product (spec) code — pair with serverImageProductCode (XEN/RHV). One of serverProductCode / serverSpecCode is required (the API rejects a request without a spec).
serverImageProductCodeNoServer image product code — for a new (public) server image, RHV/XEN. One of serverImageProductCode / serverImageNo / memberServerImageInstanceNo is required.
launchConfigurationNameNoLaunch configuration name (1-255 chars: lowercase letters, digits, '-'; auto-generated when omitted)
memberServerImageInstanceNoNoMember server image instance number — for a user-created server image. One of serverImageProductCode / serverImageNo / memberServerImageInstanceNo is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.1
    • changedInput schema / properties / initScriptNo / description
      Previous value: -"Init script number to run on launch"New value: +"Init script number to run on first boot"
    • changedInput schema / properties / isEncryptedVolume / description
      Previous value: -"Whether to encrypt the root volume"New value: +"Whether to encrypt the root volume (RHV only)"
    • changedInput schema / properties / launchConfigurationName / description
      Previous value: -"Launch configuration name"New value: +"Launch configuration name (1-255 chars: lowercase letters, digits, '-'; auto-generated when omitted)"
    • changedInput schema / properties / loginKeyName / description
      Previous value: -"Login key name for SSH access"New value: +"Login key name for SSH access (defaults to the most recently created key)"
    • changedInput schema / properties / memberServerImageInstanceNo / description
      Previous value: -"Member server image instance number (alternative to serverImageProductCode)"New value: +"Member server image instance number — for a user-created server image. One of serverImageProductCode / serverImageNo / memberServerImageInstanceNo is required."
    • addedInput schema / properties / serverImageNo
      Added value: +{
+  "description": "Server image number — for a new (public) server image (required path for KVM/Gen3). One of serverImageProductCode / serverImageNo / memberServerImageInstanceNo is required.",
+  "type": "string"
+}
    • changedInput schema / properties / serverImageProductCode / description
      Previous value: -"Server image product code"New value: +"Server image product code — for a new (public) server image, RHV/XEN. One of serverImageProductCode / serverImageNo / memberServerImageInstanceNo is required."
    • changedInput schema / properties / serverProductCode / description
      Previous value: -"Server product (spec) code"New value: +"Server product (spec) code — pair with serverImageProductCode (XEN/RHV). One of serverProductCode / serverSpecCode is required (the API rejects a request without a spec)."
    • addedInput schema / properties / serverSpecCode
      Added value: +{
+  "description": "Server spec code — pair with serverImageNo or memberServerImageInstanceNo (KVM/Gen3, e.g. c2-g3, s2-g3). One of serverProductCode / serverSpecCode is required (the API rejects a request without a spec).",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "serverImageProductCode",
-  "serverProductCode"
-]
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false, so the description carries most of the burden. It adds real behavioral context: the exactly-one-image-source invariant, the dialect-dependent spec pairing, and that dryRun returns a preview without creating. It omits auth/permission requirements and confirmation/validation failure behavior.

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?

Three dense sentences, front-loaded with the action and then the two hard constraints, with no padding or restatement of the tool name.

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?

For a 10-parameter creation tool with no output schema, the description covers the validation rules that would otherwise cause rejected requests and points at the lookup tool needed to satisfy them. It does not say what is returned (e.g. the resolved launch configuration name), which is the only notable gap.

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%, so the baseline is 3, but the description synthesizes cross-parameter wiring that individual property descriptions state only separately: the one-of image source rule and the image-source → spec-code mapping per virtualization dialect. That is genuine added meaning beyond a per-field read.

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?

States a specific verb and resource ('Create a new launch configuration for Auto Scaling') and immediately scopes it against the sibling family of list/get/delete launch-config tools. An agent can distinguish it from ncloud_create_asg and ncloud_list_launch_configs without opening a schema.

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?

Gives concrete routing guidance: which image-source parameter selects which spec parameter (XEN/RHV vs KVM) and directs the agent to ncloud_get_server_specs for valid spec codes. It also documents a safe-preview path via dryRun=true. It stops short of explicit when-not-to-use or the prerequisite relationship to ncloud_create_asg.

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

Deploy Server

Other Tools