Skip to main content
Glama

Upgrade cluster agent

upgrade_cluster_agent
Destructive

Upgrade the Ankra agent on a cluster now (the twin of ankra cluster agent upgrade), instead of waiting for the fleet rollout. Without a version it installs the newer of the release the agent runs and the latest stable release, so it never moves an agent backwards (an agent on a newer release candidate is re-rendered where it is). Pass version to install an exact published release; a version older than the running one is refused unless allow_downgrade is true, and a version that is neither published nor running is refused - relay those refusals as they are. Check get_cluster_agent_status first: the cluster must be online and have exactly one registered agent. The agent replaces itself and the cluster reads as offline for the seconds it restarts. Requires agents.manage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upgrade_cluster_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoExact agent release to install, such as 2.1.1250. Optional: without it the platform installs the newer of the running release and the latest stable one.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.
allow_downgradeNotrue lets version be older than the release the agent runs (a deliberate rollback). Needs version; without it the upgrade never moves the agent backwards. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / allow_downgrade
      Added value: +{
      +  "description": "true lets version be older than the release the agent runs (a deliberate rollback). Needs version; without it the upgrade never moves the agent backwards. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / version
      Added value: +{
      +  "description": "Exact agent release to install, such as 2.1.1250. Optional: without it the platform installs the newer of the running release and the latest stable one.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=false; the description adds the crucial operational context that the agent replaces itself and the cluster reads as offline for the seconds it restarts. It also documents the version-resolution rules and the downgrade refusal path, going well beyond what annotations convey. Minor gap: it does not say what the response looks like or whether the call blocks until the agent returns.

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?

Front-loaded with the action and the sibling contrast, and nearly every clause carries information (version rules, refusals, offline window, permission). It is a dense single block with several semicolon-chained caveats, so it is efficient but not maximally scannable.

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

Completeness5/5

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

For a 4-param destructive mutation with no output schema, the description covers preconditions, default resolution semantics, rollback gating, error-handling expectations, and the transient downtime side effect. Nothing an agent needs in order to call it safely is missing.

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 baseline is 3, but the description adds real semantics: without version it picks the newer of running vs latest stable so it never moves backwards, allow_downgrade only matters when version is passed, and older or unpublished versions are refused. That clarifies the interaction between two optional parameters that the schema states only individually.

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 ("Upgrade the Ankra agent on a cluster now") and immediately distinguishes itself from the fleet rollout path and its CLI twin. An agent can tell this apart from upgrade_cluster, upgrade_managed_cluster, and set_cluster_agent_auto_upgrade.

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 covers when to use it (immediate upgrade instead of waiting for fleet rollout), a mandated prerequisite check (get_cluster_agent_status, cluster online with exactly one registered agent), the required permission (agents.manage), and the refusal cases that must be relayed verbatim rather than worked around.

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.