KubeCraft MCP Server

List Helm Releases

helm_list

List Helm releases with status, chart, app version, and revision number, optionally scoped to a namespace.

Instructions

List Helm releases with status, chart, app version, and revision number.

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

Input Schema

Name	Required	Description	Default
`namespace`	No	Namespace (omit for all namespaces)
`all_namespaces`	No	List across all namespaces (default: true when namespace is omitted)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations exist, so the description must fully disclose behavior. It only states what is listed, without mentioning scope (e.g., cluster-wide by default), or any side effects. For a simple list tool this is minimal but acceptable, yet lacks detail about what happens with missing namespace or default behavior.

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?

One concise sentence that efficiently conveys purpose and output. It is front-loaded with the verb and resource. Slight room for improvement by grouping related info, but overall well-structured.

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?

Given no output schema, the description usefully lists the fields returned. It implies a list result. For a tool with only two simple parameters, this is sufficient, though it could mention that releases are from the current cluster context.

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%, so baseline is 3. The description does not add meaning beyond the schema; it mentions output fields but not parameter details. No additional value for parameters.

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 clearly states the verb 'list' and the resource 'Helm releases', and specifies the output fields (status, chart, app version, revision). This distinguishes it from siblings like 'flux_list_helmreleases' which lists Flux-managed releases.

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?

No guidance on when to use this tool versus alternatives such as 'helm_get_values' or other list tools. No when-not-to-use or prerequisites are mentioned.

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

Deploy Server