MCP Server Kubernetes

uninstall_helm_chart

Destructive

Remove a specified Helm chart release from a Kubernetes cluster using the given name and namespace.

Instructions

Uninstall a Helm chart release

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": {
      "name": "<name>",
      "namespace": "<namespace>"
    },
    "name": "uninstall_helm_chart"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the Helm release to uninstall
`namespace`	Yes	Kubernetes namespace	default
`context`	No	Kubeconfig Context to use for the command (optional - defaults to null)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.9.1Jun 18, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The annotation already indicates destructiveHint=true, and the description merely says 'Uninstall' which matches, but adds no extra behavioral context such as what resources are affected, reversibility, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise but lacks structure such as sections or bullet points. It is not verbose, but could be better organized.

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 operation with no output schema, the description should provide more context about side effects, return values, or safety notes. It is incomplete given the tool's nature.

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 baseline is 3. The description does not add any additional meaning to the parameters beyond what the schema already provides.

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 verb 'Uninstall' and the resource 'Helm chart release', making the tool's purpose obvious. It distinguishes from siblings like install_helm_chart and upgrade_helm_chart.

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 on when to use this tool versus alternatives, no prerequisites or exclusions. The single sentence does not provide any usage context.

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