Skip to main content
Glama

Update addon configuration

update_addon_configuration
Destructive

Replace an installed addon's helm values with a full YAML document and commit the change to the cluster's GitOps repository. Pass the COMPLETE values document (fetch it first with get_addon_configuration) - this is not a partial merge. If the fetched document contains [REDACTED:...] placeholders, replace them with the real values or drop those keys before writing; documents that still carry placeholders are rejected. Never place plaintext secrets in values; use the addon's existing secret references. Reversible via rollback_addon.

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

Input Schema

NameRequiredDescriptionDefault
valuesYesThe addon's full helm values as a base64-encoded YAML document (the same encoding get_addon_configuration returns).
addon_nameYesName of the installed addon.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, and the description adds real value on top: full-replacement semantics, rejection of [REDACTED:...] placeholders, the GitOps commit side effect, and secret-reference handling. It stops short of describing permission requirements or the response, but the added behavioral context is substantial.

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 core action and the full-replacement constraint are front-loaded, and each following sentence carries a distinct rule (fetch first, placeholder rejection, secrets, rollback). No filler.

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 destructive mutation with no output schema, the definition covers prerequisites, encoding source, failure modes and reversal. Slightly incomplete on what the call returns or whether a sync is triggered after the GitOps commit.

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 goes beyond it by clarifying that the values parameter must be the complete document rather than a partial merge and by pointing at get_addon_configuration as the source of the encoding. cluster_id and addon_name are left to the schema, which is fine.

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?

Names a specific verb and resource ('Replace an installed addon's helm values') and adds the side effect ('commit the change to the cluster's GitOps repository'). This clearly distinguishes it from siblings such as update_addon_settings or update_addon_in_stack_profile_draft.

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 directs the agent to fetch first with get_addon_configuration, states that partial merge is not supported, and names rollback_addon as the reversal path. It also gives a prohibition (no plaintext secrets) and an error condition to avoid.

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.