Skip to main content
Glama
mmpyro

vcluster-mcp

by mmpyro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vcluster_delete

Delete a virtual cluster and its resources permanently, with options to preserve the namespace or persistent volume claim. Provides idempotent cleanup if the cluster is not found.

Instructions

Delete a vcluster.

This action is irreversible - the cluster and all its resources will be permanently removed. By default the host namespace is preserved; the vcluster CLI still cleans up namespaces it created itself.

Args: name: The name of the vcluster to delete. namespace: Optional namespace where the vcluster is located. If not provided, defaults to the vcluster name. delete_namespace: If True, also delete the host namespace. DESTRUCTIVE - this removes every other workload in that namespace as well. Only set it when the namespace exists solely for this vcluster. keep_pvc: If True, retain the vcluster's persistent volume claim so the data survives the deletion. ignore_not_found: If True, succeed instead of erroring when the vcluster does not exist. Useful for idempotent cleanup. wait: If False, return immediately instead of waiting for the deletion to complete. kubeconfig_path: Optional path to a kubeconfig file. If not provided, the default kubeconfig from the environment will be used.

Returns: Union[CommandResult, str]: CommandResult on success, or error object if failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
waitNo
keep_pvcNo
namespaceNo
kubeconfig_pathNo
delete_namespaceNo
ignore_not_foundNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full transparency burden. It discloses irreversibility, host-namespace preservation, that the CLI cleans up namespaces it created, the destructive namespace deletion flag, PVC retention, not-found behavior, and wait 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 structured with a warning up front, then a labeled Args section, and then Returns. Every sentence adds necessary behavioral or parameter context for a destructive operation, with no filler.

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?

Despite the large parameter count and complete absence of annotations, the description fully covers all parameters, side effects, destructive edge cases, defaults, and the return type. No critical information is missing for an agent to decide whether to call this tool and how.

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

Parameters5/5

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

Schema description coverage is 0%, so the description is the only source of parameter meaning. It explains all seven parameters, including defaults, the destructive implications of delete_namespace, and the purpose of keep_pvc, ignore_not_found, wait, and kubeconfig_path.

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 opens with a specific verb and resource ('Delete a vcluster') and immediately clarifies the irreversibility, which separates it from sibling operations like vcluster_pause, vcluster_resume, or vcluster_create. The phrase 'permanently removed' makes the tool's purpose unmistakable.

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

Usage Guidelines4/5

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

The irreversible-warning gives clear context that this is for permanent removal rather than temporary lifecycle actions like pause/resume. It does not explicitly name alternatives or state 'use vcluster_pause for temporary stops,' so it stops short of a full 5, but the context is not merely implied.

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