vmware-vks

delete_namespace

Destructive

Permanently removes a vSphere Namespace and all resources inside it. Previews the blast radius first, then performs the irreversible deletion only after explicit confirmation.

Instructions

[WRITE] Delete a vSphere Namespace and everything inside it (irreversible).

Without confirm=True this only previews: it returns blast_radius (the namespace, and the TKC clusters, VMs and PVCs inside it, with counts and names) 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", namespace, status, blast_radius}. Refused while TKC clusters exist inside (run delete_tkc_cluster on each), and whenever the clusters, VMs or PVCs inside could not be read. Prefer update_namespace to only change quotas.

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>"
    },
    "name": "delete_namespace"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Namespace name to delete (discover via list_namespaces).
`target`	No	vCenter in config.yaml; omit for the default.
`confirm`	No	False (default) returns the blast radius and changes nothing. True applies 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"
-}

Changed9 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"
```

Changed5 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 / name / description
```
Added value: +"Namespace name to delete (discover via list_namespaces)."
```
- 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 and readOnlyHint=false, but the description adds the two-phase preview/apply contract, the exact shape of blast_radius, and the refusal conditions (existing TKC clusters, unreadable children). That is precisely the context annotations cannot express.

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-loads the destructive nature in brackets, then the preview mechanics, then the confirm contract, then the guardrails. Every sentence carries operational weight; the 'do not set confirm=True on your own' warning is the single most important line and is placed prominently.

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?

No output schema exists, yet the description states the return object for both modes ({action, namespace, status, blast_radius} vs blast_radius only), and covers the blocking conditions. An agent has everything needed to call this safely.

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 baseline is 3; however the description elaborates the confirm parameter's consequence beyond the schema's terse note, spelling out what happens in each mode and warning against self-authorizing confirm=True. It does not add anything for name or target, which the schema already handles.

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 a specific verb+resource ('Delete a vSphere Namespace') and immediately states scope ('everything inside it') and irreversibility. The closing line distinguishes it from update_namespace and delete_tkc_cluster, so an agent can route correctly without touching siblings.

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 explicit when-to-use (preview first, confirm only after user decision), when-not-to (never confirm on the strength of an earlier 'delete' utterance), prerequisites (TKC clusters must be deleted first), and the alternative for non-destructive intent (update_namespace). Nothing is left to inference.

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