Skip to main content
Glama
AlexW00

ArtifactHub MCP Server

by AlexW00

helm-chart-values

Retrieve the values.yaml configuration file for a specific Helm chart from Artifact Hub to customize 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

  • Handler function that fetches the Helm chart's values.yaml from Artifact Hub by first getting chart info, determining version, retrieving values, and returning as text content or error message.
    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}`,
    				},
    			],
    		};
    	}
    }
  • Zod input schema defining parameters: chartRepo (string), chartName (string), version (optional string).
    {
    	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)"),
    },
  • Function that registers the 'helm-chart-values' tool with the MCP server, specifying name, description, input schema, and handler.
    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}`,
    						},
    					],
    				};
    			}
    		}
    	);
    }
  • src/index.ts:18-18 (registration)
    Invokes registerValuesTool to add the tool to the main MCP server instance.
    registerValuesTool(server);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states what the tool does but doesn't cover important aspects like authentication requirements, rate limits, error conditions, or what happens when the chart/version isn't found. For a read operation with external dependencies, this is inadequate.

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 states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential 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 lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what format the values.yaml is returned in (raw text, parsed structure?), doesn't mention error scenarios, and provides no context about Artifact Hub integration. For a tool interacting with external systems, more completeness is needed.

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 adds no parameter semantics beyond what's already in the schema (which has 100% coverage). It doesn't explain the relationship between chartRepo and chartName, provide examples of valid values, or clarify what 'Artifact Hub' means in this context. Baseline 3 is appropriate since the schema does the documentation work.

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 resource ('values.yaml file for a specific Helm chart from Artifact Hub'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'helm-chart-values-fuzzy-search', which likely serves a similar purpose with different search behavior.

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. It doesn't mention alternatives like 'helm-chart-values-fuzzy-search' for approximate matching or 'helm-chart-info' for general metadata, leaving the agent without context for 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/AlexW00/artifacthub-mcp'

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