Skip to main content
Glama

Update addon settings

update_addon_settings

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.

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

A3.5/5.0
Behavior4/5

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

Annotations only say readOnly=false, idempotent=false, destructive=false; the description adds two genuinely new behaviors: partial-merge semantics ("Only the members present in the settings object change; everything else keeps its stored value") and the side effect that the change is committed to the cluster's GitOps repository. It also explains the concrete hazard of rollback re-applying stale rendered manifests. Missing are permission requirements and whether a reconcile/sync is triggered afterwards.

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 what changes, then merge semantics, then the risk caveat — a sensible ordering. The parenthetical field list largely duplicates the schema's settings description, and the final sentence is dense, but nothing is genuinely wasted or buried.

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

Completeness3/5

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

For a mutation tool with a nested object parameter, no output schema, and no clarifying annotations, the description covers mutation semantics and git-commit side effects well. It leaves open whether the new settings take effect immediately or require a subsequent sync/reconcile, and how it relates to update_addon_configuration, which matters for calling it correctly.

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 earns an extra point by adding merge semantics for the nested settings object (unspecified members are preserved) and by explaining the operational meaning and risk of rollback_on_failure rather than just naming it. cluster_id and addon_name add nothing beyond the schema, but the settings object is materially enriched.

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?

The description gives a specific verb and resource ("Update an installed addon's operational settings") and enumerates the concrete settings members, so the agent knows exactly what is mutated. It does not, however, differentiate itself from close siblings such as update_addon_configuration, update_addon_in_stack_profile_draft, or sync_addon, which a reader has to disambiguate by name alone.

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

Usage Guidelines2/5

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

There is no statement about when to choose this tool over the sibling update_addon_configuration / update_addon_in_stack_profile_draft, nor any prerequisite (e.g. addon must be installed, settings must be read first via get_addon_settings). The only conditional advice given ("Set rollback_on_failure false for a slow stateful addon...") is value-level guidance, not tool-selection guidance.

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.