vmware-vks

delete_tkc_cluster

Destructive

Deletes a Tanzu Kubernetes Cluster and all its nodes irreversibly. Preview the blast radius first, then confirm to proceed; force skips workload checks.

Instructions

[WRITE] Delete a TKC cluster and all of its nodes (irreversible).

Without confirm=True this only previews: it returns blast_radius (control plane and worker node counts per pool, and the running Deployments, StatefulSets and DaemonSets) and deletes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user said "delete" earlier: they have not seen what it destroys yet.

confirm=True returns {action: "deleted", name, namespace, status: "deleting", blast_radius}. Refused while workloads run (drain them, or pass force=True, which skips the workload check entirely) and whenever the node counts or workloads could not be read. Use scale_tkc_cluster instead for fewer nodes. Empty a namespace of TKC clusters before delete_namespace accepts it.

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": {
      "name": "<name>",
      "namespace": "<namespace>"
    },
    "name": "delete_tkc_cluster"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Cluster name (via list_tkc_clusters).
`force`	No	Skip the running-workload check (dangerous).
`target`	No	vCenter in config.yaml; omit for the default.
`confirm`	No	False (default) returns the blast radius and changes nothing. True applies it.
`namespace`	Yes	Namespace holding it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.4.2Oct 31, 2026

removedInput schema / properties / confirmed

Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews.",
-  "title": "Confirmed"
-}

removedInput schema / properties / dry_run

Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=True previews.",
-  "title": "Dry Run"
-}

Changed10 schema fields changedv1.11.0Sep 20, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "False (default) returns the blast radius and changes nothing. True applies it.",
+  "title": "Confirm",
+  "type": "boolean"
+}

addedInput schema / properties / confirmed / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / confirmed / default
```
Previous value: -falseNew value: +null
```

changedInput schema / properties / confirmed / description

Previous value: -"Must be True to proceed."New value: +"Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews."

removedInput schema / properties / confirmed / type
```
Removed value: -"boolean"
```

addedInput schema / properties / dry_run / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / dry_run / default
```
Previous value: -trueNew value: +null
```

changedInput schema / properties / dry_run / description

Previous value: -"Preview only (default: True)."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=True previews."

removedInput schema / properties / dry_run / type
```
Removed value: -"boolean"
```

changedInput schema / properties / force / description

Previous value: -"Skip the workload check (dangerous)."New value: +"Skip the running-workload check (dangerous)."

Changed7 schema fields changedv1.8.14Aug 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / confirmed / description
```
Added value: +"Must be True to proceed."
```
- addedInput schema / properties / dry_run / description
```
Added value: +"Preview only (default: True)."
```
- addedInput schema / properties / force / description
```
Added value: +"Skip the workload check (dangerous)."
```
- addedInput schema / properties / name / description
```
Added value: +"Cluster name (via list_tkc_clusters)."
```
- addedInput schema / properties / namespace / description
```
Added value: +"Namespace holding it."
```
- addedInput schema / properties / target / description
```
Added value: +"vCenter in config.yaml; omit for the default."
```
Addedv1.8.9Aug 1, 2026
Removedv1.8.8Jul 22, 2026
Addedv1.5.26May 20, 2026
Removedv1.5.23May 20, 2026
First observedv1.3.2Mar 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it discloses the preview-then-confirm mechanic, the refusal conditions (running workloads, unreadable node counts), that force=True skips the workload check entirely, and the exact return shape in both branches. That is genuine behavioral context, not a restatement of the hints.

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?

Front-loaded with the action and its irreversibility, then the preview gate, then the confirm outcome and refusal conditions. Every sentence carries safety-relevant content; none is filler or restated metadata.

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?

There is no output schema, but the description compensates by describing both return shapes (blast_radius on preview; {action, name, namespace, status, blast_radius} on confirm). Refusal modes, ordering constraints with delete_namespace, and the safe-call protocol are all covered for a destructive 5-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning beyond the schema by framing confirm as a decision gate (preview vs apply) with a policy about when the agent may set it, and by spelling out force=True's blast-radius consequence. It does not address target beyond the schema, so it is not a perfect 5.

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?

Opens with an explicit verb+resource and scope: "Delete a TKC cluster and all of its nodes (irreversible)." It also names the sibling that serves the adjacent need ("Use scale_tkc_cluster instead for fewer nodes"), so the agent can discriminate without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-phase protocol: without confirm=True it previews and deletes nothing; show the blast radius and get an explicit decision. It states a clear prohibition ("Do not set confirm=True on your own... they have not seen what it destroys yet") and names alternatives (scale_tkc_cluster, delete_namespace ordering).

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