ncloud-mcp-server

ncloud_delete_asg

DestructiveIdempotent

Permanently delete an Auto Scaling Group by providing its ID and setting confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete an Auto Scaling Group. Set confirm=true to execute.

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": {
      "autoScalingGroupNo": "<autoScalingGroupNo>"
    },
    "name": "ncloud_delete_asg"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`autoScalingGroupNo`	Yes	Auto Scaling Group number to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true. The description adds important context beyond annotations: the operation is permanent and requires confirm=true to execute. This explains the behavior of being gated by a confirmation flag, which annotations do not capture. 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 a single, front-loaded sentence with an emoji warning. It immediately conveys the destructive nature, the action, and the required confirmation step. No redundant or unnecessary words.

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 simple delete tool with two parameters and no output schema, the description covers the essential aspects: destructive action, permanence, and the confirm flag. It does not explain return values, but that is not needed without an output schema. It could mention prerequisites, but the operation is straightforward and the schema covers parameter details.

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 coverage is 100%, with both confirm and autoScalingGroupNo already described. The description's mention of 'Set confirm=true to execute' adds no new meaning beyond the schema's own description of the confirm parameter. The description does not elaborate on autoScalingGroupNo beyond what schema provides.

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 verb 'delete' and the specific resource 'Auto Scaling Group', and adds 'Permanently' to convey irreversibility. This distinguishes it from sibling tools like ncloud_delete_launch_config or ncloud_delete_vpc, which target different resources.

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

Usage Guidelines3/5

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

The description implies usage by warning 'Destructive' and 'Permanently delete', suggesting this is for intentional deletion only. However, it does not explicitly state when to use it instead of alternatives (e.g., update_asg) or provide exclusions. The confirm=true instruction is a parameter-level guideline, not a tool-level usage directive.

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

Deploy Server