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;
    }
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 authentication requirements, rate limits, error conditions, or whether this is a read-only operation (though implied by 'Get information').

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 specific details about what information is retrieved.

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?

For a simple read operation with 2 parameters and 100% schema coverage, the description is minimally adequate but lacks behavioral context needed when annotations are absent. No output schema exists, so description doesn't explain return format beyond listing data types.

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 parameters are fully documented in the schema. The description adds no additional parameter context beyond implying these identify a specific chart. Baseline 3 is appropriate when schema does the heavy lifting.

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 information') and resource ('Helm chart from Artifact Hub'), specifying what information is retrieved (ID, latest version, description). It distinguishes from siblings by focusing on basic metadata rather than templates or values, though it doesn't explicitly name alternatives.

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 for retrieving basic chart metadata, but provides no explicit guidance on when to use this tool versus sibling tools like helm-chart-template or helm-chart-values. No prerequisites, exclusions, or comparison to alternatives are mentioned.

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