Skip to main content
Glama

Install stack

install_stack
Destructive

Install an uninstalled stack again: every add-on, manifest and application uninstall_stack took off the cluster deploys again in dependency order, with the definitions the stack holds now. A member that was already off the cluster before the uninstall stays off it. Only an uninstalled stack can be installed: refused, with nothing changed, for a stack that is installed, a stack whose uninstall is still running, a stack with an open draft, a stack being deleted or down with its cluster, and a cluster that is not online. NOT reversible: the deployment jobs it starts run to completion (uninstall_stack takes the stack off again). Requires stacks.deploy.

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": "install_stack"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description corroborates this by stating the tool is NOT reversible and that its deployment jobs run to completion. It adds genuinely new behavior: dependency-ordered deployment, use of 'the definitions the stack holds now', preservation of members that were already off-cluster, fail-with-no-changes semantics, and the stacks.deploy permission requirement. The only gap is what the call returns (job ids, status), which the annotations do not cover.

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 action and follows with preconditions, refusal cases, reversibility, and permission needs in descending order of importance. Every sentence carries distinct operational information; nothing is restated from the name or schema.

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 two-parameter mutation with no output schema, the definition covers what gets deployed, in what order, under what preconditions it is refused, and that it is irreversible. An agent has enough to decide whether to call it and to anticipate the result without needing anything else.

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%, and the schema already says stack_name is 'Name of the uninstalled stack to install again' and that cluster_id is an Ankra UUID discoverable via list_clusters. The description adds no syntax, format, or constraint detail beyond that, so the baseline of 3 applies.

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 first clause states a specific verb and resource ('Install an uninstalled stack again') and immediately scopes it to what uninstall_stack removed. This clearly separates it from uninstall_stack and from apply_stack_changes, which would deploy changes to an already-installed stack.

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 gives an explicit precondition ('Only an uninstalled stack can be installed') and enumerates five refusal conditions, so an agent can self-check before calling. It also names the undo path (uninstall_stack takes the stack off again), which is the alternative an agent needs for reversal.

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.