Skip to main content
Glama

Redeploy stack

redeploy_stack
Destructive

Redeploy a stack's resources that are stuck in a transitional state (creating, updating, stopping): re-runs their deployment jobs in dependency order. Resources already covered by an in-flight operation are skipped, and the call is a no-op when nothing is transitional. NOT reversible: the triggered deployment jobs run to completion.

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

Input Schema

NameRequiredDescriptionDefault
forceNoOptional, default false. Set true only when a manifest's apply failed with an error reading conflict with "<manager>" and the person accepts the overwrite. The manifests among the resources this call re-runs then apply with server-side apply force-conflicts, for this redeploy only: nothing is stored on the stack. The result names them under forced_resource_ids: a manifest not listed there was not forced, so check that the one that failed is there before saying the conflict was taken back. Members this call does not re-run and add-ons are not forced, and an application member's apply forces conflicts either way. Force takes the conflicting fields back to the stack's values on the live objects and overwrites whatever they hold now, which Ankra cannot undo. before-first-apply is Kubernetes' name for fields written before Ankra's first server-side apply, not another controller, though the value may still be one a person set. Needs clusters.write on the cluster on top of stacks.deploy, and an approved plan does not cover it: it runs only as a call of its own.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack to redeploy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Optional, default false. Set true only when a manifest's apply failed with an error reading conflict with \"<manager>\" and the person accepts the overwrite. The manifests among the resources this call re-runs then apply with server-side apply force-conflicts, for this redeploy only: nothing is stored on the stack. The result names them under forced_resource_ids: a manifest not listed there was not forced, so check that the one that failed is there before saying the conflict was taken back. Members this call does not re-run and add-ons are not forced, and an application member's apply forces conflicts either way. Force takes the conflicting fields back to the stack's values on the live objects and overwrites whatever they hold now, which Ankra cannot undo. before-first-apply is Kubernetes' name for fields written before Ankra's first server-side apply, not another controller, though the value may still be one a person set. Needs clusters.write on the cluster on top of stacks.deploy, and an approved plan does not cover it: it runs only as a call of its own.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: declares the operation is NOT reversible because the triggered deployment jobs run to completion, explains the dependency-order execution, the skipping of in-flight resources, and the no-op case. This is consistent with destructiveHint=true and idempotentHint=false and adds meaningful consequence detail an agent cannot get from the annotations.

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?

Three tight sentences, front-loaded with what it does and the transitional-state qualifier, then the skip/no-op behavior, then the irreversibility warning last for emphasis. No filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter destructive mutation with no output schema and rich annotations plus a fully-documented schema, the description covers purpose, trigger, and consequences adequately. Minor gap: it does not hint at how to confirm the outcome (e.g. inspecting the resulting deployment jobs), though the schema's force entry partially covers result verification.

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 force parameter is documented at length in the schema itself (conflict semantics, forced_resource_ids, permissions, plan exclusion). The prose description adds no parameter-level meaning of its own, 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?

States a specific verb (redeploy) and resource (a stack's resources) plus a precise scope: only resources stuck in a transitional state (creating, updating, stopping), re-running their deployment jobs in dependency order. That scoping naturally sets it apart from broader siblings like apply_stack_changes or resync-flavoured tools without needing to name them.

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

Usage Guidelines4/5

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

Explicit trigger condition ('stuck in a transitional state') and explicit when-not behavior: resources covered by an in-flight operation are skipped and the call is a no-op when nothing is transitional, which tells the agent not to bother. It stops short of naming an alternative tool for the overlapping cases (e.g. apply_stack_changes), so it is strong but not a full when/when-not/alternatives treatment.

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.