ncloud-mcp-server

ncloud_nks_delete_addon

DestructiveIdempotent

Remove an add-on from an NKS cluster. Pass confirm=true to execute the uninstall.

Instructions

⚠️ Destructive: Uninstall an add-on from an NKS cluster. 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": {
      "clusterUuid": "<clusterUuid>",
      "addonRef": "<addonRef>"
    },
    "name": "ncloud_nks_delete_addon"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to execute
`addonRef`	Yes	Installed add-on reference: the add-on name OR the installed add-on's UUID
`clusterUuid`	Yes	UUID of the cluster

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 already provide destructiveHint=true and idempotentHint=true. The description adds value by explaining the confirmation mechanism ('Set confirm=true to execute') and reinforcing the destructive nature with a warning emoji. This goes beyond the 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 sentence with an emoji, efficiently conveying the action, destructive warning, and execution requirement. No superfluous 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?

Given the three parameters are fully described in the schema, and annotations provide the safety profile, the description is complete enough. It explains the critical execution condition (confirm=true) and the destructive nature. No output schema exists, so return values are not expected.

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?

The input schema has 100% description coverage, so the schema already explains all three parameters. The description only reiterates the confirm parameter's purpose. It adds little beyond the schema, meeting the baseline of 3.

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 action: 'Uninstall an add-on from an NKS cluster.' It specifies the resource (add-on) and the target (NKS cluster), and mentions the critical 'confirm' parameter. This distinguishes it from sibling tools like ncloud_nks_update_addon or ncloud_nks_install_addons.

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 warns 'Destructive' and instructs to set confirm=true, but it does not explicitly state when to use this tool versus alternatives (e.g., when to use ncloud_nks_update_addon instead). The usage context is implied but not directly clarified.

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

Deploy Server