Skip to main content
Glama
mmpyro

vcluster-mcp

by mmpyro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vcluster_delete

Delete a virtual cluster irreversibly, preserving host namespace by default. Optionally keep persistent volumes or delete the host namespace when dedicated.

Instructions

Delete a vcluster. Irreversible. The host namespace is preserved by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
waitNo
keep_pvcNoRetain the persistent volume claim so data survives the deletion.
namespaceNo
kubeconfig_pathNo
delete_namespaceNoDESTRUCTIVE: also delete the host namespace, removing every other workload in it. Only for a namespace that exists solely for this vcluster.
ignore_not_foundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / delete_namespace / description
      Added value: +"DESTRUCTIVE: also delete the host namespace, removing every other workload in it. Only for a namespace that exists solely for this vcluster."
    • addedInput schema / properties / keep_pvc / description
      Added value: +"Retain the persistent volume claim so data survives the deletion."
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "CommandResult": {
-      "properties": {
-        "exit_code": {
-          "title": "Exit Code",
-          "type": "integer"
-        },
-        "output": {
-          "title": "Output",
-          "type": "string"
-        }
-      },
-      "required": [
-        "exit_code",
-        "output"
-      ],
-      "title": "CommandResult",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "result": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/CommandResult"
-        },
-        {
-          "additionalProperties": {
-            "type": "string"
-          },
-          "type": "object"
-        },
-        {
-          "type": "string"
-        }
-      ],
-      "title": "Result"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "vcluster_deleteOutput",
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / delete_namespace
      Added value: +{
+  "default": false,
+  "title": "Delete Namespace",
+  "type": "boolean"
+}
    • addedInput schema / properties / ignore_not_found
      Added value: +{
+  "default": false,
+  "title": "Ignore Not Found",
+  "type": "boolean"
+}
    • addedInput schema / properties / keep_pvc
      Added value: +{
+  "default": false,
+  "title": "Keep Pvc",
+  "type": "boolean"
+}
    • addedInput schema / properties / wait
      Added value: +{
+  "default": true,
+  "title": "Wait",
+  "type": "boolean"
+}
  3. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral disclosure burden. It does disclose two key traits: deletion is irreversible, and the host namespace is preserved by default. However, it omits other important behaviors such as wait blocking by default, PVC deletion semantics, and the destructive potential of delete_namespace, which is only covered in the schema, not the description.

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?

Three short sentences with no filler. The key facts—delete action, irreversibility, and default namespace preservation—are front-loaded and each sentence contributes meaning. This is an excellent example of concise, structured tool documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 7 parameters, no annotations, no output schema, and low schema description coverage. The description covers only the headline destructive behavior and one default. It does not address blocking behavior, data survival, namespace targeting, kubeconfig handling, or not-found behavior, leaving the agent under-equipped to invoke it correctly in varied scenarios.

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

Parameters2/5

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

Schema description coverage is only 29%, so the description should compensate for under-documented parameters. It adds partial meaning by clarifying the default for delete_namespace ('host namespace is preserved by default'), but it says nothing about name, wait, keep_pvc, namespace, kubeconfig_path, or ignore_not_found. The compensation is insufficient for a 7-parameter destructive operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Delete a vcluster.' It adds meaningful scope notes ('Irreversible. The host namespace is preserved by default.') that go beyond mere repetition of the tool name. It does not explicitly distinguish from sibling tools, but the delete action itself is clearly differentiated from list, describe, create, pause, and resume.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives, nor any exclusions or prerequisites. The description implies 'use this to delete a vcluster,' but it does not discuss cases like pausing instead of deleting, or when keep_pvc or delete_namespace should be set. This leaves the agent to infer usage from the tool name alone.

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