Skip to main content
Glama

helm_uninstall

Uninstall a Helm release from a Kubernetes cluster and remove all resources it created; require confirmed=True to proceed, with False providing a dry-run preview.

Instructions

Uninstall a Helm release from a cluster. Destructive — requires confirmed=True.

Removes all Kubernetes resources created by the release.

Write operation — recorded in the audit log.

Args: cluster_name: Target cluster. release_name: Name of the Helm release to remove. namespace: Kubernetes namespace (default: 'default'). confirmed: Must be True to proceed. Pass False (default) for a dry-run preview. gateway_id: Gateway UUID from list_clusters. Omit for single-gateway deployments; provide to disambiguate when multiple gateways share a cluster name.

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": {
      "cluster_name": "<cluster_name>",
      "release_name": "<release_name>"
    },
    "name": "helm_uninstall"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedNo
namespaceNodefault
gateway_idNo
cluster_nameYes
release_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.72.5
    • addedInput schema / properties / confirmed
      Added value: +{
      +  "default": false,
      +  "title": "Confirmed",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it labels the tool destructive and a write operation, states it is recorded in the audit log, names the gating flag, and warns that all resources created by the release are removed. That is exactly the safety profile an agent needs before calling a delete-shaped tool.

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 front-loaded with the destructive warning and confirmation requirement before any argument detail, and the Args block is scannable with one line per parameter. No sentence is filler; even the audit-log note is behaviorally relevant.

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

Completeness4/5

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

For a five-parameter destructive tool with no annotations and no output schema, the definition covers purpose, risk, gating, and every argument. The one gap is that it does not say what a dry-run preview returns, which matters given the confirmed=False path is explicitly offered as a safe first step.

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 must supply all parameter meaning, and it does: every one of the five parameters is documented with its purpose, and the two defaults (namespace='default', confirmed=False) plus the gateway_id disambiguation rule are spelled out. This adds substantive meaning the bare JSON schema lacks.

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 opens with a specific verb+resource ("Uninstall a Helm release from a cluster") and immediately clarifies scope ("Removes all Kubernetes resources created by the release"). It never names the obvious counterpart helm_upgrade, so sibling differentiation is left implicit in the verb rather than stated.

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?

It gives concrete operational guidance: confirmed=True is required to proceed, confirmed=False yields a dry-run preview, and gateway_id should be omitted for single-gateway deployments but supplied when cluster names collide. What's missing is any statement of when to prefer this over related tools such as helm_upgrade or a generic delete.

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