Skip to main content
Glama

Uninstall stack

uninstall_stack
Destructive

Uninstall a stack: take every add-on, manifest and application of the stack off its cluster, in reverse dependency order, while the stack stays declared in Ankra and in Git, so install_stack brings it back later. Unlike delete_stack, nothing is removed from Ankra or Git. Data is treated exactly as a delete treats it: whatever a chart or operator removes with its workload is gone (an operator that owns its volume claims, such as CloudNativePG, deletes them and their data), so when the stack holds data, suggest a backup first (protect_stack with backup_now=true). Refused, with nothing changed, for a cluster that is not online, a stack with an open draft, a stack with a member whose deployment has not finished, a stack being deleted or down with its cluster, and a stack a managed service owns (retire the service instead). An uninstall of a stack that is already uninstalled with nothing up on the cluster has nothing to take off and is answered as such. Requires stacks.delete.

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>",
      "cluster_id": "<cluster_id>"
    },
    "name": "uninstall_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack to uninstall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say destructiveHint=true; the description goes far beyond by explaining the data-loss semantics (an operator owning its volume claims, e.g. CloudNativePG, deletes the data), the refusal set for which nothing changes, the auth requirement (stacks.delete), and the already-uninstalled case. idempotentHint=false is consistent with the statement that preconditions are refused rather than retried, so no contradiction.

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?

Front-loaded with the core action and its scope, then the destructive consequence, then preconditions and the permission — a sensible ordering with no filler sentences. It is a single dense block, though, so the refusal list and data-loss warning could be more scannable.

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 two-parameter tool with no output schema, the definition covers everything an agent needs: what is removed, what persists, ordering, irreversible data consequences, prerequisites, refusal cases, and required permission. Nothing material is deferred to annotations or schema.

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?

Both parameters are fully documented in the schema (100% coverage), including how to discover cluster_id via list_clusters, so the baseline applies. The description only alludes to the cluster indirectly ('off its cluster'); it adds no format, naming, or resolution guidance beyond the schema.

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?

States a specific verb (uninstall) and resource (stack), then enumerates exactly what is removed — add-ons, manifests, applications — and in what order (reverse dependency). It explicitly contrasts with delete_stack (nothing removed from Ankra or Git) and names install_stack as the inverse, so the agent can distinguish it from siblings without opening another 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?

Gives positive guidance (tear workloads off the cluster while keeping the stack declared, reinstallable later) plus a concrete alternative for the data-safety case (protect_stack with backup_now=true when the stack holds data). It also enumerates precise when-not conditions: cluster offline, open draft, unfinished member deployment, stack being deleted, stack down with its cluster, and managed-service ownership (retire the service instead).

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.