ncloud-gov-mcp-server

ncloud_hadoop_delete_cluster

DestructiveIdempotent

Permanently delete a Cloud Hadoop cluster and its data. Specify the instance number and set confirm=true to complete the deletion.

Instructions

⚠️ Destructive: Permanently delete a Cloud Hadoop 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": {
      "cloudHadoopInstanceNo": "<cloudHadoopInstanceNo>"
    },
    "name": "ncloud_hadoop_delete_cluster"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to execute deletion
`regionCode`	No	Region code
`cloudHadoopInstanceNo`	Yes	Cloud Hadoop instance number to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotation destructiveHint is reinforced by the description's explicit 'All data will be lost' warning, which explains the consequence. The confirm=true requirement adds safety context that annotations do not provide, giving the agent a clear understanding of the operation's irreversibility and the required gate.

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 plus a short imperative, front-loading the destructive warning and stating the action, consequence, and required confirmation in about 20 words. Every phrase earns its place with no redundancy.

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 destructive delete tool with three parameters and no output schema, the description covers the essential purpose, consequence, and activation prerequisite. It omits details about return values or behavior for nonexistent clusters, but these are not critical given the schema covers parameters and annotations cover idempotency.

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 descriptions for cloudHadoopInstanceNo, confirm, and regionCode. The description only reiterates the confirm parameter's role ('Set confirm=true to execute'), adding no additional meaning for the other parameters. Thus the baseline 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 explicitly states 'Permanently delete a Cloud Hadoop cluster,' identifying the exact action (delete) and resource (Cloud Hadoop cluster). This distinguishes it from sibling tools that delete notebooks or other cluster types, such as ncloud_ses_delete_cluster or ncloud_nks_delete_cluster.

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 does not mention alternatives or when to avoid using this tool. However, it clearly implies use only when deleting a Cloud Hadoop cluster is intended and establishes a necessary precondition: 'Set confirm=true to execute.' This provides basic usage guidance but lacks explicit comparison to alternatives.

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

Deploy Server