Skip to main content
Glama

List Helm releases

list_helm_releases
Read-only

Every Helm release actually installed on the cluster, read live through the agent (the twin of ankra cluster helm releases): name, namespace, revision, status, chart and app version - including releases Ankra did not deploy. Compare with list_addons to find drift outside the GitOps record. Read-only; uninstalling is not available here.

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": "list_helm_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many releases to return (default 100, at most 500); the result says when it was truncated.
namespaceNoOnly releases in this namespace. Omit for every namespace.
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
name_filterNoRegular expression the release name must match (at most 200 characters).
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, but the description adds real behavioral context beyond that: the data is read live through the agent rather than from the Ankra record, and the result includes releases Ankra never deployed. That provenance distinction materially changes how an agent should interpret and trust the output.

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?

The scope and field list are front-loaded in the first clause, and each following sentence adds a distinct fact (drift comparison, no uninstall). The parenthetical CLI twin reference is mildly expendable for an agent that has no shell, but the rest is dense and waste-free.

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?

There is no output schema, so the description compensates by enumerating the returned fields and noting that results can include non-Ankra releases. Pagination/truncation behavior is already covered in the limit parameter's schema text, so nothing an agent needs to call this 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 description coverage is 100%, so limit, namespace, cluster_id, name_filter and cluster_name are already fully documented in the input schema, including the regex constraint and the 500 cap. The description adds no filter or targeting semantics of its own, so the baseline of 3 applies.

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?

The description names a specific verb and resource ('list every Helm release actually installed on the cluster') and enumerates the returned fields (name, namespace, revision, status, chart, app version). It explicitly scopes the result to include releases Ankra did not deploy, which separates it from the GitOps-record views in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit comparison point — 'Compare with list_addons to find drift outside the GitOps record' — which tells an agent exactly why to call this rather than the addon tools. It also closes off a wrong expectation with 'uninstalling is not available here', though it doesn't name a sibling for the case where the caller does want to modify a release.

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.