vmware-vks

delete_tkc_cluster

Destructive

Preview a TKC cluster's deletion impact (node counts, running workloads), then confirm to irreversibly delete the cluster and all nodes. Refuses while workloads run unless force is set.

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.

Input Schema

TableJSON 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.
`dry_run`	No	Deprecated alias for confirm; removed in the next minor release. dry_run=True previews.
`confirmed`	No	Deprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews.
`namespace`	Yes	Namespace holding it.

Schema Changelog

Changes observed during successful MCP inspections.

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?

Beyond the destructiveHint=true annotation, the description reveals the irreversible nature, the preview mode returning blast_radius, the refusal conditions while workloads run, and the force flag's effect of skipping the workload check. It also states what confirm=True returns, giving the agent a clear model of the tool's behavior.

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 long but every sentence carries essential safety or routing information for a destructive tool with no output schema. It is front-loaded with the irreversible destructive action, then explains the preview flow, refusal conditions, and alternatives in a logical order with no redundancy.

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?

Since there is no output schema, the description properly explains return values for both preview and confirmed deletion, including blast_radius contents. It also covers failure/refusal cases, the force escape hatch, deprecated aliases, and sibling-tool routing, making it complete for an agent to call this tool correctly.

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?

The schema already covers all parameters with 100% description coverage, but the tool description adds important context beyond it: confirm=False previews, confirm=True deletes, force=True skips the workload check, and dry_run/confirmed are deprecated aliases. This adds real semantic value on top of the schema.

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 states a specific verb and resource: 'Delete a TKC cluster and all of its nodes (irreversible).' It clearly differentiates from siblings by explicitly directing agents to scale_tkc_cluster for fewer nodes and noting delete_namespace requires an empty namespace. This gives an unambiguous purpose.

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?

The description gives explicit when-to-use and when-not-to-use guidance: it instructs the agent to preview without confirm=True, never set confirm=True unilaterally, and drain workloads or use force=True only when appropriate. It also names scale_tkc_cluster and delete_namespace as alternatives, so the agent can route correctly.

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

delete_tkc_cluster

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools