ncloud-gov-mcp-server

ncloud_nks_delete_cluster

DestructiveIdempotent

Permanently delete an NKS Kubernetes cluster. Requires confirm=true to execute the destructive action.

Instructions

⚠️ Destructive: Permanently delete an NKS Kubernetes 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>"
    },
    "name": "ncloud_nks_delete_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`clusterUuid`	Yes	UUID of the cluster to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds critical behavior: the operation is permanent and requires explicit confirmation via the confirm parameter. This goes beyond the annotation by explaining the execution guard, which is essential for an agent to use the tool safely.

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 compact and front-loaded, with the destructive warning first, then the action, then the required confirmation. Every sentence serves a distinct purpose and there is no redundant filler.

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

Completeness5/5

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

For a destructive delete tool with only two parameters, full schema coverage, and annotations providing safety hints, the description is sufficient. It covers the purpose, the confirmation requirement, and the permanence, leaving no critical gaps.

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 both confirm and clusterUuid clearly described in the input schema. The description's mention of 'Set confirm=true' reinforces the confirm parameter's role but adds no new parameter-specific detail beyond what the schema already 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 action ('Permanently delete') and the resource ('an NKS Kubernetes cluster'), leaving no ambiguity about what the tool does. This distinguishes it from sibling tools like ncloud_nks_list_clusters or ncloud_nks_create_cluster.

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 clear operational guidance by warning that the operation is destructive and requiring 'confirm=true to execute'. It does not explicitly name alternatives or exclusions, but the context of permanent deletion clearly implies this is for removing an entire cluster, not for partial operations like node pool deletion.

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

Deploy Server