ncloud-gov-mcp-server

ncloud_cdss_delete_cluster

DestructiveIdempotent

Permanently delete a CDSS (Kafka) cluster. Requires confirm=true to execute; all data will be lost.

Instructions

⚠️ Destructive: Permanently delete a CDSS (Kafka) cluster. All data will be lost. 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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>"
    },
    "name": "ncloud_cdss_delete_cluster"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to execute deletion
`serviceGroupInstanceNo`	Yes	Cluster instance number to delete (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint. The description adds value by specifying the concrete consequence ('All data will be lost') and the mandatory confirm flag, which is not evident from the annotations alone. 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 extremely concise: three short sentences with high information density. The warning emoji and front-loaded 'Destructive' immediately catch attention, and every clause (permanent deletion, data loss, confirm requirement) earns its place.

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 2-parameter delete operation with full schema coverage and appropriate annotations, the description covers the essential operational aspects: the destructive action, data-loss consequence, and the confirmation gate. A minor gap is not stating what happens when confirm=false, but the default 'false' and schema description imply a no-op.

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 already covers both parameters with descriptions (confirm defaulting to false, serviceGroupInstanceNo as required). The description reinforces the confirm requirement but does not add semantic detail beyond the schema, and with 100% schema coverage, the baseline of 3 applies.

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 ('delete') and the specific resource ('CDSS (Kafka) cluster'), and adds the critical qualifier 'permanently' with 'All data will be lost.' This distinguishes it from other delete tools such as ncloud_cdss_delete_config_group.

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 destructive warning and the explicit 'Set confirm=true to execute' provide clear usage context, signaling that this is a high-risk operation requiring confirmation. However, it does not explicitly compare with alternative tools or state when not to use it, so it stops short of full guidance.

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

Deploy Server