Skip to main content
Glama

helm_upgrade

Deploy or update a Helm chart on a Kubernetes cluster with a dry-run preview first; requires confirmed=True to apply destructive changes.

Instructions

Run helm upgrade --install for a chart on a cluster. Destructive — requires confirmed=True.

On an existing release this replaces the running workloads, so it is gated like any other destructive action: call once to get the dry-run preview, then again with confirmed=True.

Use this for Helm chart deployments. For deploying standard AI models, use deploy_model instead.

Write operation — recorded in the audit log.

Args: cluster_name: Target cluster. release_name: Helm release name (created if it does not exist). chart: Helm chart reference (e.g. bitnami/nginx or ./charts/myapp). namespace: Kubernetes namespace (default: 'default'). values: Helm values to override (dict, optional). confirmed: Must be True to proceed. Pass False (default) for a dry-run preview. gateway_id: Gateway UUID from list_clusters. Omit for single-gateway deployments; provide to disambiguate when multiple gateways share a cluster name.

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": {
      "cluster_name": "<cluster_name>",
      "release_name": "<release_name>",
      "chart": "<chart>"
    },
    "name": "helm_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartYes
valuesNo
confirmedNo
namespaceNodefault
gateway_idNo
cluster_nameYes
release_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.72.5
    • addedInput schema / properties / confirmed
      Added value: +{
      +  "default": false,
      +  "title": "Confirmed",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does most of it: it discloses the destructive nature, that existing workloads are replaced, the confirmation gate, the audit-log record, and the --install create-if-absent behavior. It stops short of failure/rollback semantics and what the dry-run preview actually contains, which matters for a destructive write.

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 operation and the destructive warning, then the gating protocol, then routing, then args — good ordering. There is minor redundancy: "Destructive — requires confirmed=True" is restated in the second paragraph and again in the confirmed arg, costing a little density without adding information.

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 7-parameter destructive tool with no annotations and no output schema, the description covers selection, sequencing, and every parameter adequately. The remaining gap is return-side: since no output schema exists, the description could say what the dry-run preview yields, which an agent needs to act on step one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the Args block is doing real work: it gives chart reference examples (bitnami/nginx, ./charts/myapp), the namespace default, that release_name is created if absent, that values are overrides, and that gateway_id comes from list_clusters and is only needed to disambiguate across gateways. This meaningfully exceeds the bare property titles in the 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?

"Run helm upgrade --install for a chart on a cluster" names the specific verb and resource, and the follow-up sentence separates it from deploy_model by workload type. An agent can distinguish it from helm_uninstall and deploy_model without opening any schema.

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?

It states the two-step protocol explicitly (call once for a dry-run preview, then again with confirmed=True) and names the alternative (deploy_model) with the condition that selects it. Both when-to-use and how-to-sequence are given, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools