Skip to main content
Glama

List chart versions

list_chart_versions
Read-only

List the available catalog versions for one Helm chart, newest first (semver ordering). Returns the latest version, the ordered version list, the registries that carry the chart, and the version currently pinned in the loaded draft when the chart is part of it. Use this to pick an upgrade target before update_addon_config, or to verify that a requested chart_version exists. list_available_charts only shows the single latest version per chart - this is the tool for the full version history.

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": {
      "chart_name": "<chart_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "list_chart_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_nameYesChart name exactly as listed by list_available_charts (case-insensitive).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
registry_nameNoOptional registry name or URL to filter by when multiple registries carry the chart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the return-shape burden and does it well: latest version, semver-ordered list, carrying registries, and the version pinned in the loaded draft when applicable. It does not mention how a chart absent from the draft, or an unknown chart_name, is handled, which is the remaining 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?

Three sentences, zero waste: purpose and ordering front-loaded, then use cases, then the sibling disambiguation. Every sentence earns its place.

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?

With no output schema, the description supplies the return fields an agent needs to interpret results, and all three parameters are covered by the schema. Nothing required to call it correctly is missing.

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 coverage is 100% and each parameter is documented in the schema, including the registry filter's purpose. The description adds no meaning beyond that – it never mentions registry_name or how the draft-pin field relates to cluster_id. Baseline 3 applies when the schema does the heavy lifting.

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 ('List the available catalog versions for one Helm chart'), adds the ordering (newest first, semver), and explicitly contrasts with list_available_charts so the agent can differentiate without opening either 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?

Gives two concrete use cases ('pick an upgrade target before update_addon_config' and 'verify that a requested chart_version exists') and names the alternative sibling plus the condition that selects it ('only shows the single latest version per chart'). Explicit when-to-use and when-not-to-use.

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.