Skip to main content
Glama
hd-deman

ArtifactHub MCP Server

by hd-deman

helm-chart-info

Retrieve Helm chart metadata from Artifact Hub, including version details and descriptions for specified chart repositories and names.

Instructions

Get information about a Helm chart from Artifact Hub, including ID, latest version, and description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartRepoYesThe Helm chart repository name
chartNameYesThe Helm chart name

Implementation Reference

  • The handler logic for helm-chart-info which calls getChartInfo and formats the response.
    	async ({ chartRepo, chartName }: InfoParams) => {
    		try {
    			const data = await getChartInfo(chartRepo, chartName);
    
    			return {
    				content: [
    					{
    						type: "text",
    						text: JSON.stringify(
    							{
    								id: data.package_id,
    								latest_version: data.version,
    								description: data.description,
    							},
    							null,
    							2
    						),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Error retrieving chart info: ${(error as Error).message}`,
    					},
    				],
    			};
    		}
    	}
    );
  • src/tools/info.ts:7-46 (registration)
    The registration of the helm-chart-info tool.
    export function registerInfoTool(server: McpServer) {
    	return server.tool(
    		"helm-chart-info",
    		"Get information about a Helm chart from Artifact Hub, including ID, latest version, and description",
    		{
    			chartRepo: z.string().describe("The Helm chart repository name"),
    			chartName: z.string().describe("The Helm chart name"),
    		},
    		async ({ chartRepo, chartName }: InfoParams) => {
    			try {
    				const data = await getChartInfo(chartRepo, chartName);
    
    				return {
    					content: [
    						{
    							type: "text",
    							text: JSON.stringify(
    								{
    									id: data.package_id,
    									latest_version: data.version,
    									description: data.description,
    								},
    								null,
    								2
    							),
    						},
    					],
    				};
    			} catch (error) {
    				return {
    					content: [
    						{
    							type: "text",
    							text: `Error retrieving chart info: ${(error as Error).message}`,
    						},
    					],
    				};
    			}
    		}
    	);
  • The helper function that performs the API request to retrieve chart information.
    export async function getChartInfo(
    	chartRepo: string,
    	chartName: string
    ): Promise<ArtifactHubPackage> {
    	const url = `https://artifacthub.io/api/v1/packages/helm/${encodeURIComponent(
    		chartRepo
    	)}/${encodeURIComponent(chartName)}`;
    	return (await fetchFromArtifactHub(url)) as ArtifactHubPackage;
    }
  • The parameter schema for the helm-chart-info tool.
    export interface InfoParams {
    	chartRepo: string;
    	chartName: string;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
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 only states what information is returned. It doesn't disclose behavioral aspects like rate limits, authentication requirements, error conditions, pagination, or response format. The description is minimal beyond stating the basic operation.

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?

Single sentence with zero waste - every word contributes to understanding the tool's purpose. Front-loaded with the core action and resource, followed by source and specific return details. Appropriately sized for this simple tool.

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?

For a tool with no annotations and no output schema, the description is too minimal. It doesn't explain what format the information comes in, whether it's a single object or list, error handling, or any limitations. The description should provide more context given the lack of structured metadata.

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%, so the schema already documents both parameters adequately. The description doesn't add any parameter-specific context beyond what's in the schema descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get information'), resource ('Helm chart'), source ('from Artifact Hub'), and specific information included ('ID, latest version, and description'). It distinguishes from siblings by focusing on general chart metadata rather than templates or values.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing basic chart metadata from Artifact Hub, but doesn't explicitly state when to use this tool versus alternatives like the fuzzy-search siblings or template/value-specific tools. No explicit exclusions or comparison to siblings are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.