ncloud-gov-mcp-server

ncloud_nks_delete_worker_node

DestructiveIdempotent

Delete a specific worker node from an NKS cluster by instance number. Requires confirm=true to execute this destructive action.

Instructions

⚠️ Destructive: Delete a specific worker node 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>",
      "instanceNo": "<instanceNo>"
    },
    "name": "ncloud_nks_delete_worker_node"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to execute
`instanceNo`	Yes	Instance number of the worker node to delete
`clusterUuid`	Yes	UUID of the cluster

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?

The description reinforces the destructiveHint annotation with a warning emoji and adds the confirm-gating behavior, which is not fully captured by annotations alone. The idempotentHint is not contradicted or elaborated, but the description adds meaningful safety context.

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 a concise warning prefix. Every word earns its place—it states the action, the target, and the critical execution requirement without fluff.

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, three-parameter tool with clear annotations and schema, the description covers the essential behavior: destructive action, target, and confirmation gate. It lacks details about prerequisites or post-conditions, but these are not critical given the tool's simplicity and the presence of annotations and schema.

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 for all three parameters, including the confirm flag's meaning. The description adds no new parameter information but does highlight the confirm=true requirement, which is redundant with the schema. Baseline 3 is appropriate.

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'), the resource ('specific worker node'), and the context ('from an NKS cluster'). It distinguishes from sibling tools like ncloud_nks_delete_node_pool by specifying 'specific worker node' rather than a node pool.

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 a clear context for use (deleting a worker node) and a critical usage requirement ('Set confirm=true to execute'). It does not mention alternatives or exclusions, but the confirm flag is a strong, actionable guideline.

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

Deploy Server