Skip to main content
Glama

Rollback addon

rollback_addon
Destructive

Roll back an addon to an earlier version. An Argo CD addon rolls back to a revision from get_addon_history (pass revision). An Ankra native addon rolls back its chart version as a declared rollback: pass chart_version (the older version to return to), from_chart_version (the version get_addon_details says it is declared at now) and reason. The native rollback is refused if the addon is no longer declared at from_chart_version, or if chart_version is not older than it.

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

Input Schema

NameRequiredDescriptionDefault
reasonNoAnkra native addons only: why the rollback is needed. Recorded with the rollback.
revisionNoArgo CD addons only: the revision number to roll back to. Use get_addon_history to see available revisions.
addon_nameYesName of the addon to rollback.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
chart_versionNoAnkra native addons only: the older chart version to roll back to.
from_chart_versionNoAnkra native addons only: the chart version the addon is declared at now (from get_addon_details). The rollback is refused if it has moved since.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description doesn't need to re-establish that it mutates. It adds real value beyond them by disclosing server-side guard rails: the native rollback is refused if the addon has moved off from_chart_version or if chart_version is not strictly older. What is missing is the effect on live workloads after a successful rollback.

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 the action, then the two variants, then the refusal rules. Dense but every clause carries operational meaning. Slightly heavy on parenthetical cross-references, though none are wasted.

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 description covers prerequisites, per-mode parameters, and preconditions that cause rejection. It stops short of describing post-rollback state (e.g. whether workloads redeploy or config drift is reverted), which would make it fully self-sufficient.

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 further by tying parameters to addon types and to the sibling tools that supply their values, and by defining the ordering constraint between chart_version and from_chart_version. That relational meaning is not fully expressible in the flat schema.

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 and resource ('Roll back an addon to an earlier version') and immediately splits the operation into two concrete modes: Argo CD addons via 'revision' and Ankra native addons via 'chart_version'. An agent can tell exactly what this does and how it differs from neighbours like upgrade_cluster or sync_addon.

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?

Names the prerequisite discovery tools for each mode ('revision from get_addon_history', 'from_chart_version ... from get_addon_details'), which effectively routes the agent to the right calls before invoking. It also states the refusal conditions. It does not explicitly say when to prefer this over a plain re-sync or upgrade, but the mode selection guidance is clear.

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.