Skip to main content
Glama
vmware-skills

vmware-vks

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_namespace

Destructive

Preview the blast radius, then permanently delete a vSphere Namespace and everything inside it 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNamespace name to delete (discover via list_namespaces).
targetNovCenter in config.yaml; omit for the default.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
dry_runNoDeprecated alias for confirm; removed in the next minor release. dry_run=True previews.
confirmedNoDeprecated alias for confirm; removed in the next minor release. Acts only together with dry_run=False; confirmed=False previews.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.11.0
    • 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"
  2. Changed5 schema fields changedv1.8.14
    • 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."
  3. Addedv1.8.9
  4. Removedv1.8.8
  5. Addedv1.5.26
  6. Removedv1.5.23
  7. First observedv1.3.2

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses irreversible destruction, preview-only behavior, refusal conditions when inner resources cannot be read, and the returned blast_radius structure. The behavior is fully transparent.

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 dense but every sentence earns its place, covering purpose, safety, refusal conditions, return shape, and alternatives. The critical warning is front-loaded and clearly separated from supporting details.

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?

For a destructive, irreversible tool with no output schema, the description covers the action, the preview mechanism, the return values, the blocking conditions, and the recommended sibling tool. Nothing an agent needs to call it safely is missing.

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, but the description adds operational semantics: confirm=False previews, confirm=True returns {action: 'deleted', namespace, status, blast_radius}, and deprecated aliases are clarified in context. This goes beyond the schema field descriptions.

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?

Description clearly states a specific verb and resource: 'Delete a vSphere Namespace and everything inside it (irreversible).' It distinguishes itself from siblings by warning it refuses while TKC clusters exist and by directing users to update_namespace for quota-only changes.

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?

Provides explicit when-to-use and when-not-to-use guidance: preview with confirm=False, show blast_radius to the user, never set confirm=True autonomously, run delete_tkc_cluster on existing TKC clusters first, and prefer update_namespace for quota changes. This is unusually complete.

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

Deploy Server

Other Tools