ncloud-gov-mcp-server

ncloud_create_asg

Create an Auto Scaling Group with specified launch configuration, subnets, and instance size limits. Use dryRun to preview the ASG without creating it.

Instructions

Create a new Auto Scaling Group. Use dryRun=true to preview without creating.

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": {
      "launchConfigurationNo": "<launchConfigurationNo>",
      "subnetNoList": "<subnetNoList>",
      "minSize": "<minSize>",
      "maxSize": "<maxSize>"
    },
    "name": "ncloud_create_asg"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, returns a preview without actually creating
`maxSize`	Yes	Maximum number of instances
`minSize`	Yes	Minimum number of instances
`subnetNoList`	Yes	List of subnet numbers for the ASG
`defaultCooldown`	No	Default cooldown period in seconds
`desiredCapacity`	No	Desired number of instances
`serverNamePrefix`	No	Prefix for server instance names
`targetGroupNoList`	No	List of target group numbers to attach
`healthCheckTypeCode`	No	Health check type (SVR or LOADB)
`autoScalingGroupName`	No	Auto Scaling Group name
`launchConfigurationNo`	Yes	Launch configuration number to use
`healthCheckGracePeriod`	No	Health check grace period in seconds
`accessControlGroupNoList`	No	List of ACG numbers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations declare destructiveHint=false, and the description does not contradict this. The description adds useful dryRun behavior (preview without creating), which is beyond the annotation. However, it does not disclose other behavioral aspects such as possible cost implications, prerequisites like an existing launch configuration, or that creation may be asynchronous. The dryRun insight is helpful but not comprehensive.

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 exceptionally concise: two short sentences that front-load the core purpose and immediately mention the dryRun option. Every word earns its place, with no redundant content or unnecessary detail.

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?

For a create tool with 13 parameters and no output schema, the description is somewhat sparse. It omits what the response will contain (e.g., created ASG details) and does not mention prerequisites like needing a launch configuration or subnet list (though these are in required schema). The dryRun preview is a nice touch, but the description could be more complete regarding return behavior and setup expectations.

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?

Schema description coverage is 100%, with every parameter already described in the input schema. The tool description adds no extra parameter semantics beyond highlighting dryRun (which is already in the schema). Baseline 3 is appropriate since the schema handles parameter documentation.

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 Auto Scaling Group', which is a specific verb+resource combination. It distinguishes from sibling tools like ncloud_delete_asg, ncloud_list_asgs, and ncloud_update_asg by focusing on the creation action. The dryRun hint adds further functional clarity.

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 makes it evident this tool is for creating a new ASG, and the dryRun=true guidance provides a preview alternative before actual creation. However, it does not explicitly mention when not to use it or compare with alternatives like update_asg or set_desired_capacity, though the creation context is clearly implied.

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

Deploy Server