MCP (Model Context Protocol) server library exposing jhelm operations as AI tools for Helm chart rendering, inspection, and linting
jhelm provides 5 read-only Helm tools with complete input schemas and clear descriptions. All tools follow verb_noun naming (helm_template, helm_show_*, helm_lint). Descriptions are adequate (100-150 chars) and explain what each tool does. However, output schemas are not documented, LLMs cannot predict return structure. Parameter descriptions are present but minimal (10-30 chars); some lack format/constraint details. No error handling guidance. All tools are read-only (low risk), but lack the depth expected for production-grade tools.
Lint a Helm chart for problems (like 'helm lint') and return errors and warnings. Read-only.
Show a chart's Chart.yaml metadata (like 'helm show chart'). Read-only.
Show a chart's README (like 'helm show readme'). Read-only.
Show a chart's default values.yaml (like 'helm show values'). Read-only.
Render a Helm chart's templates locally (like 'helm template') and return the generated Kubernetes manifests as YAML. Read-only; does not touch any cluster.
Output schemas not documented. LLMs cannot predict return structure (fields, types, nesting). Breaks downstream tool chaining and forces agents to guess at response format.
Parameter descriptions are minimal (10-30 chars). E.g., 'Path to the chart directory or packaged .tgz archive' is adequate, but 'Target Kubernetes namespace' lacks guidance on format/constraints. No mention of valid namespace patterns or length limits.
No error handling guidance. If a chart path is invalid or a namespace does not exist, LLMs receive raw errors with no recovery hints. Should include: 'If chart not found, verify path is absolute or relative to current directory.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
helm_template has 7 optional parameters (showOnly, skipTests, includeCrds, isUpgrade) with no guidance on mutual exclusivity or common combinations. LLMs may pass conflicting flags.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). While all tools are read-only, explicit annotations would signal safety to agents and enable optimizations.