Skip to main content
Glama

helm-list

List Helm releases in Kubernetes clusters to view deployed applications and their status, optionally filtered by namespace.

Instructions

List Helm releases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoThe namespace to list releases from (optional, defaults to all namespaces)

Implementation Reference

  • Handler that executes the 'helm list' command with an optional namespace to list Helm releases and returns the output.
    case "helm-list": {
      const { namespace } = args || {};
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `helm list ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "No Helm releases found" }]
      };
    }
  • Tool definition including name, description, and input schema for 'helm-list', which accepts an optional namespace parameter.
      name: "helm-list",
      description: "List Helm releases",
      inputSchema: {
        type: "object",
        properties: {
          namespace: { 
            type: "string",
            description: "The namespace to list releases from (optional, defaults to all namespaces)"
          }
        }
      }
    },
  • server.js:1392-1394 (registration)
    Registers the handler for ListToolsRequestSchema, which returns the full list of tools including 'helm-list'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List Helm releases' implies a read-only operation, but it doesn't specify whether this requires special permissions, how results are formatted (e.g., table vs. JSON), if it includes deleted releases, or any pagination/limiting behavior. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise with just three words ('List Helm releases'), front-loading the core purpose without any wasted words. It's appropriately sized for a simple listing tool with minimal parameters.

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 lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what a 'Helm release' is in this context, what information is returned (e.g., release names, statuses, versions), or how this differs from other listing tools. For a tool in a complex Kubernetes/Helm environment with many siblings, more contextual information would be helpful.

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%, with the single parameter 'namespace' well-documented in the schema as optional and defaulting to all namespaces. The description adds no additional parameter information beyond what the schema provides, which is acceptable given the high schema coverage, resulting in a baseline score of 3.

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 'List Helm releases' clearly states the verb ('List') and resource ('Helm releases'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list-all' or 'list-pods' that also list resources, nor does it specify what 'Helm releases' are compared to other Kubernetes resources.

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. With many sibling tools like 'list-all', 'list-pods', and other Helm-specific tools (e.g., 'helm-install', 'helm-status'), there's no indication of when this specific Helm listing tool is appropriate or what distinguishes it from general resource listing tools.

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