Skip to main content
Glama

helm-uninstall

Remove a Helm release from a Kubernetes cluster by specifying its name and optional namespace to clean up deployed applications and resources.

Instructions

Uninstall a Helm release

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the release
namespaceNoThe namespace of the release (optional, defaults to current context namespace)

Implementation Reference

  • Handler for the helm-uninstall tool. Parses arguments for release name and optional namespace, constructs and executes the 'helm uninstall' command via execAsync, and returns the command output or a success message.
    case "helm-uninstall": {
      const { name, namespace } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `helm uninstall ${name} ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || `Helm release ${name} uninstalled` }]
      };
    }
  • server.js:1235-1251 (registration)
    Tool registration entry in the tools array, including name, description, and inputSchema for validation. This is returned by the ListToolsRequestHandler.
      name: "helm-uninstall",
      description: "Uninstall a Helm release",
      inputSchema: {
        type: "object",
        properties: {
          name: { 
            type: "string",
            description: "The name of the release"
          },
          namespace: { 
            type: "string",
            description: "The namespace of the release (optional, defaults to current context namespace)"
          }
        },
        required: ["name"]
      }
    },
  • Input schema defining the expected arguments: required 'name' (string) and optional 'namespace' (string). Used for tool call validation.
    inputSchema: {
      type: "object",
      properties: {
        name: { 
          type: "string",
          description: "The name of the release"
        },
        namespace: { 
          type: "string",
          description: "The namespace of the release (optional, defaults to current context namespace)"
        }
      },
      required: ["name"]
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the destructive action ('Uninstall') but doesn't mention critical details like whether this is irreversible, what happens to associated resources, permission requirements, or error handling. For a destructive operation with zero annotation coverage, this is inadequate.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, immediately conveying the core purpose without unnecessary elaboration.

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?

For a destructive tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'uninstall' entails operationally, what gets removed, potential side effects, or return values. Given the complexity and risk of Helm uninstallation, more context is needed.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters ('name' and 'namespace') adequately. The description doesn't add any additional meaning about parameters beyond what the schema provides, such as format constraints or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Uninstall') and target ('a Helm release'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'helm-list' or 'helm-upgrade' beyond the obvious action difference.

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?

No guidance is provided about when to use this tool versus alternatives like 'delete' for non-Helm resources or 'helm-upgrade' for updates. The description lacks context about prerequisites, dependencies, or typical scenarios for uninstalling Helm releases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server