Skip to main content
Glama
hd-deman

ArtifactHub MCP Server

by hd-deman

helm-chart-values

Retrieve the values.yaml file for a specific Helm chart from Artifact Hub to configure and customize Kubernetes deployments.

Instructions

Get the values.yaml file for a specific Helm chart from Artifact Hub

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartRepoYesThe Helm chart repository name
chartNameYesThe Helm chart name
versionNoThe chart version (optional, defaults to latest)

Implementation Reference

  • The handler logic for the 'helm-chart-values' tool, which fetches chart information and then the values.yaml.
    	async ({ chartRepo, chartName, version }: ValuesParams) => {
    		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 values.yaml
    			const valuesYaml = await getChartValues(packageId, chartVersion);
    
    			return {
    				content: [
    					{
    						type: "text",
    						text: valuesYaml,
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Error retrieving values.yaml: ${(error as Error).message}`,
    					},
    				],
    			};
    		}
    	}
    );
  • Registration of the 'helm-chart-values' tool within the MCP server.
    export function registerValuesTool(server: McpServer) {
    	return server.tool(
    		"helm-chart-values",
    		"Get the values.yaml file for a specific Helm chart from Artifact Hub",
    		{
    			chartRepo: z.string().describe("The Helm chart repository name"),
    			chartName: z.string().describe("The Helm chart name"),
    			version: z
    				.string()
    				.optional()
    				.describe("The chart version (optional, defaults to latest)"),
    		},
    		async ({ chartRepo, chartName, version }: ValuesParams) => {
    			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 values.yaml
    				const valuesYaml = await getChartValues(packageId, chartVersion);
    
    				return {
    					content: [
    						{
    							type: "text",
    							text: valuesYaml,
    						},
    					],
    				};
    			} catch (error) {
    				return {
    					content: [
    						{
    							type: "text",
    							text: `Error retrieving values.yaml: ${(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 'Get[s] the values.yaml file', implying a read-only operation, but does not clarify aspects like authentication requirements, rate limits, error handling, or the format of the returned values. This leaves significant gaps in understanding the tool's behavior beyond its basic purpose.

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, direct sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the key action and resource, making it easy to parse quickly, and every part of the sentence contributes essential information.

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 (3 parameters, no output schema, no annotations), the description is minimally complete for a read operation. It specifies the resource and source (Artifact Hub), but lacks details on output format, error cases, or integration with siblings. This is adequate for basic use but leaves room for improvement in guiding effective tool selection and invocation.

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 input schema has 100% description coverage, clearly documenting all three parameters (chartRepo, chartName, version) with their types and optionality. The description does not add any additional semantic details beyond what the schema provides, such as examples or constraints, so it meets the baseline for adequate but not enhanced parameter understanding.

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') and the resource ('values.yaml file for a specific Helm chart from Artifact Hub'), making the purpose immediately understandable. However, it does not explicitly differentiate this tool from its sibling 'helm-chart-values-fuzzy-search', which likely serves a similar purpose with different functionality, leaving some ambiguity in sibling distinction.

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 its siblings, such as 'helm-chart-info' or 'helm-chart-values-fuzzy-search'. It lacks any context about prerequisites, alternatives, or specific scenarios where this tool is preferred, offering minimal usage direction.

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