Skip to main content
Glama
This connector has been deprecated

Replaced by Control Plane.

This listing has been renamed. Control Plane is now listed as com.controlplane/mcp.

It is the same server at the same endpoint (https://mcp.cpln.io/mcp), so existing connections keep working. Please use the new listing going forward.

Upgrade Template

upgrade_template
Destructive

Upgrade an installed release to a new version (omit it for the latest available) with its complete values. Identify the release by name only: the template and GVC are immutable and read from the installed release, so you do NOT pass them. values REPLACE the release's current values entirely (no merge): start from the values it runs with now, which the user reads in the Console and never pastes into the chat, not the template example. Verify with get_installed_template after.

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": {
      "name": "<name>",
      "values": "<values>"
    },
    "name": "upgrade_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization slug.
nameYesRelease name — the unique, immutable identifier for this installed instance within the org.
valuesYesThe complete values.yaml for the release going forward — it REPLACES the currently applied values entirely (there is no reuse-values merge). Preserve the release's CURRENT non-sensitive settings, not the template example, or customized settings fall back to defaults. The user can inspect current values privately in the Console; never fetch or paste credential-bearing values into chat. If current values require literal credentials, upgrade privately in the Console instead.
versionNoTarget version to upgrade to. Omit for the latest available version.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNoThe full result. Read this, not only the summary.
detailsNo
summaryYes
nextStepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / name / maxLength
      Removed value: -63
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • removedInput schema / properties / name / pattern
      Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"
    • changedInput schema / properties / org / description
      Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."
    • removedInput schema / properties / org / maxLength
      Removed value: -63
    • removedInput schema / properties / org / minLength
      Removed value: -1
    • removedInput schema / properties / org / pattern
      Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"
    • changedInput schema / properties / values / description
      Previous value: -"The complete values.yaml for the release going forward — it REPLACES the currently applied values entirely (there is no reuse-values merge). Start from the release's CURRENT values (CLI: `cpln helm get values <RELEASE> --all`; there is no MCP path), not the template example, or previously customized settings silently fall back to defaults."New value: +"The complete values.yaml for the release going forward — it REPLACES the currently applied values entirely (there is no reuse-values merge). Preserve the release's CURRENT non-sensitive settings, not the template example, or customized settings fall back to defaults. The user can inspect current values privately in the Console; never fetch or paste credential-bearing values into chat. If current values require literal credentials, upgrade privately in the Console instead."
    • removedInput schema / properties / values / maxLength
      Removed value: -131072
    • removedInput schema / properties / values / minLength
      Removed value: -1
    • removedInput schema / properties / version / maxLength
      Removed value: -40
    • removedInput schema / properties / version / minLength
      Removed value: -1
    • removedInput schema / properties / version / pattern
      Removed value: -"^[A-Za-z0-9][A-Za-z0-9.+-]*$"
    • changedInput schema / required
      Previous value: -[
      -  "org",
      -  "name",
      -  "values"
      -]New value: +[
      +  "name",
      +  "values"
      +]
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / data / description
      Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."
    • addedOutput schema / properties / details
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / nextSteps / description
      Removed value: -"Recommended follow-up actions for this task, in order."
    • removedOutput schema / properties / ok / description
      Removed value: -"Whether the call succeeded."
    • removedOutput schema / properties / summary / description
      Removed value: -"One-line summary of the result."
  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 destructiveHint=true and idempotentHint=false, and the description explains *why* it is destructive: `values` REPLACE the current values entirely with no merge, so omitted customized settings fall back to defaults. It also flags the immutable template/GVC and prescribes a verification step. It does not describe rollback or failure behavior, so it stops short of a 5.

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 its main hazard, and every sentence carries a constraint. It is slightly over-dense, and the clause about values the user 'reads in the Console and never pastes into the chat' is convoluted and partly restates the schema.

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 destructive 4-parameter mutation with an output schema, the description covers the identification rule, the version default, the replacement semantics of `values`, the credential safety boundary, and a post-call verification path. Nothing an agent needs to invoke it correctly 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 the baseline is 3, but the description adds routing meaning beyond the schema: identify the release by `name` only and deliberately omit template/GVC, and where the replacement values must come from (the release's current settings, not the template example). Some of the replace-vs-merge wording duplicates the `values` schema text.

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 an installed release to a new version, with an explicit default (omit version = latest). It clearly separates itself from install_template, uninstall_template and get_installed_template by scoping to an already-installed release and by pointing at get_installed_template only for verification.

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?

Gives explicit when-to-use conditions (omit `version` for latest) and an explicit when-not/alternative: if the current values require literal credentials, upgrade privately in the Console instead. It also pre-empts a common misuse by stating the template and GVC must not be passed.

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.