Skip to main content
Glama

Update stack

update_stack
Destructive

Update an existing deployed stack on the cluster. The stack object uses the same shape as create_stack and stack.name selects the stack to update. By default the update is PARTIAL: members present in the spec are added or updated and omitted members are preserved. Set replace_missing=true to replace the whole stack, removing members missing from the spec. Dependency order is carried by each member's parents: a member added here with no parents deploys in PARALLEL with everything else, so give any member that needs a namespace, Secret, ConfigMap, CRD, operator, or database from this stack a parent for it ({"name": "", "kind": "addon", "manifest" or "application"}, kind lowercase; update_stack writes no applications, so an application parent names one already in this stack). On an existing member, OMITTING parents preserves its current edges and passing [] CLEARS them - restate the full parent list, as get_stack_details lists it with any application parent, whenever you re-send a member that has dependencies. Use this tool to add the missing edges to a stack that was created without them. Deployment of the changed members starts immediately and the change is pushed to the cluster's GitOps repository when one is connected. NEVER pass raw secret values - use ${SECRET_SLOT:} sentinels; raw secret-looking values are refused. Manifests carrying cluster-scoped or cluster-critical kinds (CustomResourceDefinition, ClusterRole, webhook configurations, PersistentVolume, ...), documents in protected namespaces (kube-, ankra-), or bindings to cluster-admin are refused by policy unless semantically unchanged from the deployed stack - manage those through the UI.

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

Input Schema

NameRequiredDescriptionDefault
stackYesThe stack specification: name selects the stack; addons and manifests carry the members to add or update, with the parents that order them. agents_md records durable operational learnings beside a member in GitOps (omit to preserve, empty string to clear).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / stack / properties / addons / items / properties / parents / items / properties / kind / description
      Previous value: -"Lowercase 'addon' or 'manifest'."New value: +"Lowercase 'addon', 'manifest' or 'application'. An application parent is an application of this stack, as get_stack_details lists it."
    • changedInput schema / properties / stack / properties / addons / items / properties / parents / items / properties / kind / enum
      Previous value: -[
      -  "addon",
      -  "manifest"
      -]New value: +[
      +  "addon",
      +  "manifest",
      +  "application"
      +]
    • changedInput schema / properties / stack / properties / manifests / items / properties / parents / items / properties / kind / description
      Previous value: -"Lowercase 'addon' or 'manifest'."New value: +"Lowercase 'addon', 'manifest' or 'application'. An application parent is an application of this stack, as get_stack_details lists it."
    • changedInput schema / properties / stack / properties / manifests / items / properties / parents / items / properties / kind / enum
      Previous value: -[
      -  "addon",
      -  "manifest"
      -]New value: +[
      +  "addon",
      +  "manifest",
      +  "application"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / stack / properties / addons / items / properties / configuration / properties / encrypted_paths / description
      Added value: +"Extra keys to seal with SOPS when the stack is committed to GitOps, e.g. \"stringData.password\" or \"auth.password\" (sops matches the last key name at any depth). A key holding a ${SECRET_SLOT:<id>} sentinel is sealed automatically and needs no entry; list a key here only to seal a value that is not a sentinel."
    • addedInput schema / properties / stack / properties / manifests / items / properties / encrypted_paths / description
      Added value: +"Extra keys to seal with SOPS when the stack is committed to GitOps, e.g. \"stringData.password\" or \"auth.password\" (sops matches the last key name at any depth). A key holding a ${SECRET_SLOT:<id>} sentinel is sealed automatically and needs no entry; list a key here only to seal a value that is not a sentinel."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations flag this as a non-idempotent destructive mutation, and the description adds substantial context beyond them: changes deploy immediately, are pushed to the connected GitOps repo, raw secret-looking values are refused in favor of ${SECRET_SLOT:<id>} sentinels, and cluster-scoped/protected-namespace/cluster-admin content is policy-refused unless semantically unchanged. These are real failure modes an agent must anticipate.

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?

Purpose is front-loaded and every sentence carries operational weight, with no filler. It is a single dense block with stacked parentheticals that make the dependency-ordering rules slower to parse than necessary, but the length is defensible for a destructive nested-spec mutation.

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 nested-spec, destructive tool with no output schema, it covers partial-vs-replace semantics, dependency ordering, secret handling, and policy refusals. The gaps are the phantom replace_missing parameter and no hint about what a successful call returns or how the agent should verify the result.

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 coverage is 100%, so the baseline is 3, and the description does add genuine meaning about parent edges (omit preserves, [] clears, restate the full list from get_stack_details). However it references replace_missing=true, a parameter that does not exist anywhere in the input schema, which is a substantive inconsistency that could cause a malformed call.

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?

Opens with a specific verb+resource+scope: 'Update an existing deployed stack on the cluster.' It also distinguishes itself from create_stack by noting the stack object 'uses the same shape as create_stack' and that 'stack.name selects the stack to update', so an agent can tell the two apart without opening schemas.

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?

Explicitly contrasts the default PARTIAL update against replace_missing=true for full replacement, and gives a named scenario: 'Use this tool to add the missing edges to a stack that was created without them.' It further states when to restate parents versus pass [] and points to get_stack_details as the read path, which is exactly the when/when-not guidance an agent needs.

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.