Skip to main content
Glama

Uninstall addon from stack

uninstall_addon_from_stack
Destructive

Mark an addon for uninstallation from a deployed stack. The agent uninstalls the addon's release, which removes its objects from the cluster; data its chart or operator deletes on uninstall is gone either way (an operator that owns its volume claims, such as CloudNativePG, deletes them and their data). Use this for direct removal of a single addon without going through the draft system. delete_permanently defaults to false (the same default as the REST API): Ankra keeps the addon's definition so it can be restored, not its cluster objects or data. Pass delete_permanently=true only when the user explicitly wants the addon permanently deleted. An addon of a stack a managed service owns is refused: retire the service instead.

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": {
      "stack_name": "<stack_name>",
      "addon_name": "<addon_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "uninstall_addon_from_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
addon_nameYesName of the addon to uninstall.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack containing the addon.
delete_permanentlyNoIf true, the addon is fully removed. If false, Ankra keeps its definition so it can be restored; its cluster objects, and any data its chart deletes on uninstall, are removed either way. Defaults to false. Pass true to permanently delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains what is actually destroyed: cluster objects are removed either way, and data deleted by the chart or operator (including operator-owned PVCs such as CloudNativePG) is irrecoverably gone. It also clarifies the default non-permanent behavior: Ankra keeps the addon definition but not the cluster objects or data, and describes the managed-service ownership refusal.

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

Conciseness4/5

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

The description is front-loaded with the core action, then moves through data-loss behavior, default semantics, and the managed-service edge case. It is somewhat dense, but every sentence carries distinct operational information and no sentence is redundant.

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?

For a destructive mutation with no output schema, the description covers the key operational facts: what is removed, what data loss is possible, what the default leaves behind, when to override it, and the managed-service exception with an alternative. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds decision guidance for delete_permanently beyond the schema by emphasizing the default and restricting true to explicit user intent, and it ties stack_name/addon_name to the concrete removal target, though it does not add syntax details for those parameters.

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 names the exact action (mark an addon for uninstallation from a deployed stack) and distinguishes this direct-removal path from the draft system and from rollback-style siblings. An agent can tell what this tool does without opening the schema.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool (direct removal of a single addon, not through the draft system) and when not to (addons owned by a managed service should be retired instead). It also gives a precise condition for delete_permanently=true: only when the user explicitly wants permanent deletion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.