Skip to main content
Glama
hd-deman

ArtifactHub MCP Server

by hd-deman

helm-chart-template

Retrieve template file content from Helm charts on Artifact Hub by specifying repository, chart name, and exact filename to analyze Kubernetes package configurations.

Instructions

Get the content of a template file from a Helm chart in Artifact Hub

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartRepoYesThe Helm chart repository name
chartNameYesThe Helm chart name
filenameYesExact filename (full path) to filter templates by (case-sensitive)
versionNoThe chart version (optional, defaults to latest)

Implementation Reference

  • Registration and implementation handler for the 'helm-chart-template' tool.
    export function registerTemplateTool(server: McpServer) {
    	return server.tool(
    		"helm-chart-template",
    		"Get the content of a template file from a Helm chart in Artifact Hub",
    		{
    			chartRepo: z.string().describe("The Helm chart repository name"),
    			chartName: z.string().describe("The Helm chart name"),
    			filename: z
    				.string()
    				.describe(
    					"Exact filename (full path) to filter templates by (case-sensitive)"
    				),
    			version: z
    				.string()
    				.optional()
    				.describe("The chart version (optional, defaults to latest)"),
    		},
    		async ({ chartRepo, chartName, filename, version }: TemplatesParams) => {
    			try {
    				let packageId: string;
    				let chartVersion: string;
    
    				// First get the chart info
    				const chartInfo = await getChartInfo(chartRepo, chartName);
    				packageId = chartInfo.package_id;
    
    				// If version is not provided, use the latest version
    				chartVersion = version || chartInfo.version;
    
    				// Get the templates
    				const templatesResult = await getChartTemplates(
    					packageId,
    					chartVersion
    				);
    
    				// Filter templates by exact filename match
    				const filteredTemplates = templatesResult.templates.filter(
    					(template) => template.name === filename
    				);
    
    				// Format the response
    				const formattedResponse = filteredTemplates
    					.map((template) => {
    						return `--- Template: ${template.name} ---\n${template.content}\n\n`;
    					})
    					.join("");
    
    				return {
    					content: [
    						{
    							type: "text",
    							text:
    								formattedResponse ||
    								"No matching templates found for this chart",
    						},
    					],
    				};
    			} catch (error) {
    				return {
    					content: [
    						{
    							type: "text",
    							text: `Error retrieving templates: ${(error as Error).message}`,
    						},
    					],
    				};
    			}
    		}
    	);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves template content but doesn't mention critical aspects like authentication requirements, rate limits, error handling (e.g., what happens if the file doesn't exist), or the format of the returned content. For a tool that interacts with an external service (Artifact Hub), this is a significant gap in transparency.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('Get the content'), making it easy to parse. There's no wasted verbiage or redundant information.

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 complexity of interacting with Helm charts and Artifact Hub, the description is incomplete. With no annotations and no output schema, it fails to address key behavioral aspects (e.g., authentication, errors, return format) and doesn't differentiate from sibling tools. While the schema covers parameters well, the overall context for safe and effective use is lacking.

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?

The description doesn't add any parameter-specific information beyond what's already in the schema (which has 100% coverage). It implies the tool operates on Helm charts in Artifact Hub, but the schema already describes parameters like 'chartRepo', 'chartName', and 'filename' with clear descriptions. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate with additional insights.

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 content') and resource ('a template file from a Helm chart in Artifact Hub'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'helm-chart-templates-fuzzy-search' (which likely searches templates rather than retrieving exact files) or 'helm-chart-info' (which provides chart metadata), leaving some ambiguity about when to choose this specific tool.

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 sibling tools like 'helm-chart-templates-fuzzy-search' (for searching templates) or 'helm-chart-values' (for retrieving values files), nor does it specify prerequisites or constraints beyond what's implied by the parameters. This lack of context could lead to incorrect tool selection.

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/hd-deman/artifacthub-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server