Skip to main content
Glama

helm-upgrade

Upgrade a Helm release in Kubernetes by specifying the release name and chart reference, with optional namespace and values overrides.

Instructions

Upgrade a Helm release

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the release
chartYesThe chart reference (repo/chart or path)
namespaceNoThe namespace of the release (optional, defaults to current context namespace)
valuesNoValues to override (YAML string)

Implementation Reference

  • The handler logic for the 'helm-upgrade' tool. It constructs a 'helm upgrade' command using the provided release name, chart, namespace, and values, executes it via execAsync, and returns the stdout or a success message.
    case "helm-upgrade": {
      const { name, chart, namespace, values } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const valuesArg = values ? `-f <(echo '${values}')` : "";
      const cmd = `helm upgrade ${name} ${chart} ${nsArg} ${valuesArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || `Helm release ${name} upgraded` }]
      };
    }
  • server.js:1208-1233 (registration)
    The tool registration entry in the 'tools' array, including name, description, and inputSchema which defines the parameters for the helm-upgrade tool.
    {
      name: "helm-upgrade",
      description: "Upgrade a Helm release",
      inputSchema: {
        type: "object",
        properties: {
          name: { 
            type: "string",
            description: "The name of the release"
          },
          chart: { 
            type: "string",
            description: "The chart reference (repo/chart or path)"
          },
          namespace: { 
            type: "string",
            description: "The namespace of the release (optional, defaults to current context namespace)"
          },
          values: { 
            type: "string",
            description: "Values to override (YAML string)"
          }
        },
        required: ["name", "chart"]
      }
    },
  • The inputSchema definition for the helm-upgrade tool, specifying the structure and requirements for input arguments.
    inputSchema: {
      type: "object",
      properties: {
        name: { 
          type: "string",
          description: "The name of the release"
        },
        chart: { 
          type: "string",
          description: "The chart reference (repo/chart or path)"
        },
        namespace: { 
          type: "string",
          description: "The namespace of the release (optional, defaults to current context namespace)"
        },
        values: { 
          type: "string",
          description: "Values to override (YAML string)"
        }
      },
      required: ["name", "chart"]
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action ('upgrade') without disclosing behavioral traits. It doesn't mention whether this is a destructive operation, requires specific permissions, has side effects (e.g., pod restarts), rate limits, or what happens on failure. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with zero waste—'Upgrade a Helm release' directly conveys the core purpose without unnecessary words. Every part earns its place, making it highly efficient for quick comprehension.

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

Completeness2/5

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

Given the complexity of a Helm upgrade operation (a mutation with potential side effects), no annotations, and no output schema, the description is incomplete. It lacks crucial context like what 'upgrade' entails (e.g., rolling updates, version changes), error handling, or expected outcomes, leaving significant gaps for an AI agent to infer behavior.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 4 parameters (name, chart, namespace, values) with their types and basic descriptions. The description adds no additional meaning beyond what's in the schema, such as explaining parameter interactions or providing examples, but meets the baseline for high schema coverage.

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 'Upgrade a Helm release' clearly states the action (upgrade) and resource (Helm release), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like helm-install or helm-uninstall, which would require mentioning specific upgrade behaviors or constraints.

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?

The description provides no guidance on when to use this tool versus alternatives like helm-install for initial deployment or helm-uninstall for removal. There's no mention of prerequisites (e.g., existing release), typical scenarios (e.g., updating chart version), or exclusions, leaving usage context entirely implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thekaranpargaie/kube-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server