Skip to main content
Glama

Update addon settings

update_addon_settings
Destructive

Update an installed addon's operational settings (sync policy, sync window, retry policy, ignore differences, revision history limit, strict health check, rollback on failure, keep failed resources for debug). Only the members present in the settings object change; everything else keeps its stored value. Set rollback_on_failure false for a slow stateful addon whose health wait can outlive the job deadline: a rollback re-applies the previous revision's rendered manifests, which can resurrect superseded content such as rotated-away credentials. The change is committed to the cluster's GitOps repository.

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

Input Schema

NameRequiredDescriptionDefault
settingsYesThe settings members to change: any of sync_policy (object), sync_window (object), retry_policy (object), ignore_differences (array), revision_history_limit (integer), strict_health_check (boolean), rollback_on_failure (boolean), keep_failed_resources_for_debug (boolean).
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/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, yet the description adds substantial context beyond them: partial-merge semantics ('only the members present in the settings object change'), the fact that changes are committed to the cluster's GitOps repository, and a specific hazard that a rollback re-applies the previous revision's rendered manifests and can resurrect superseded content like rotated-away credentials. That is exactly the kind of consequence-disclosure a mutation tool needs.

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?

Three sentences, front-loaded with purpose then merge semantics then the operational warning, with no filler. The rollback sentence is long, but it carries genuinely decision-relevant risk information rather than restating the schema.

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, non-idempotent mutation with no output schema, the description covers what changes, what is preserved, where the change lands (GitOps repo), and the main failure-mode caveat. It stops short of stating permission/auth requirements or what the call returns on success, leaving a modest gap.

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% and the settings sub-object already lists every member type, so the schema carries the baseline. The description still adds meaning the schema cannot express: that only supplied members are modified and all others retain stored values, which is the key semantic for a nested partial-update object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update an installed addon's operational settings') and enumerates the exact settings members covered, so an agent can tell this apart from get_addon_settings. It does not explicitly distinguish itself from update_addon_configuration or update_addon_in_stack_profile_draft, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

It gives one concrete conditional recommendation ('Set rollback_on_failure false for a slow stateful addon whose health wait can outlive the job deadline'), which is real when-to-use guidance for a parameter choice. However, it never says when to prefer this tool over sibling mutation tools such as update_addon_configuration, and offers no exclusions or prerequisites.

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.