Skip to main content
Glama

helm-status

Check the deployment status of a Helm release in Kubernetes to monitor application health and troubleshoot issues.

Instructions

Get the status of a Helm release

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
releaseYesThe name of the Helm release
namespaceNoThe namespace of the release (optional, defaults to current context namespace)

Implementation Reference

  • The handler function for the 'helm-status' tool. It destructures the release name and optional namespace from input arguments, constructs a 'helm status' command, executes it using execAsync, and returns the stdout as text content or an error message.
    case "helm-status": {
      const { release, namespace } = args;
      const nsArg = namespace ? `-n ${namespace}` : "";
      const cmd = `helm status ${release} ${nsArg}`;
      const { stdout } = await execAsync(cmd);
      return {
        content: [{ type: "text", text: stdout || "Unable to get Helm release status" }]
      };
    }
  • The input schema definition for the 'helm-status' tool, specifying required 'release' parameter and optional 'namespace', used for validation and tool listing.
      name: "helm-status",
      description: "Get the status of a Helm release",
      inputSchema: {
        type: "object",
        properties: {
          release: { 
            type: "string",
            description: "The name of the Helm release"
          },
          namespace: { 
            type: "string",
            description: "The namespace of the release (optional, defaults to current context namespace)"
          }
        },
        required: ["release"]
      }
    },
  • server.js:1392-1394 (registration)
    The ListToolsRequestHandler that registers all tools, including 'helm-status', by returning the tools array containing its definition.
    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 full burden for behavioral disclosure. While 'Get the status' implies a read-only operation, it doesn't explicitly state whether this requires specific permissions, whether it's safe to run, what the output format looks like, or any rate limits. For a tool that presumably queries cluster state with no annotation coverage, this leaves significant behavioral questions unanswered.

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, efficient sentence that immediately conveys the core purpose without any wasted words. It's appropriately sized for a simple status-checking tool and front-loads the essential information. Every word earns its place in this minimal but complete statement of function.

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

Completeness3/5

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

Given the tool's moderate complexity (querying Helm release status) and the absence of both annotations and output schema, the description is minimally adequate but leaves gaps. It identifies what the tool does but doesn't provide behavioral context, usage guidance, or output information. For a tool that interacts with Helm releases in a Kubernetes environment, more context about what 'status' includes and typical use cases 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 both parameters clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema fields. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description, which applies here.

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 clearly states the action ('Get the status') and target resource ('Helm release'), making the purpose immediately understandable. It distinguishes from siblings like helm-install, helm-list, helm-uninstall, and helm-upgrade by focusing on status retrieval rather than installation, listing, removal, or updating operations. However, it doesn't explicitly differentiate from rollout-status, which also deals with status but for different resource types.

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. It doesn't mention when to choose helm-status over helm-list (which might show status information), rollout-status (for deployment rollouts), or other status-checking tools. There's no context about prerequisites, typical use cases, or situations where this tool would be preferred or inappropriate.

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