Skip to main content
Glama
hd-deman

ArtifactHub MCP Server

by hd-deman

helm-chart-values-fuzzy-search

Search Helm chart values.yaml files using fuzzy matching to find properties, values, and comments across ArtifactHub repositories.

Instructions

Fuzzy search through all properties/values/comments in a Helm chart's values.yaml file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartRepoYesThe Helm chart repository name
chartNameYesThe Helm chart name
searchQueryYesThe search query for fuzzy matching
versionNoThe chart version (optional, defaults to latest)

Implementation Reference

  • The handler function implementing the fuzzy search logic for Helm chart values using Fuse.js.
    	async ({
    		chartRepo,
    		chartName,
    		searchQuery,
    		version,
    	}: FuzzySearchParams) => {
    		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);
    
    			// Parse YAML to get the value
    			const parsedYaml = parse(valuesYaml);
    			const doc = parseDocument(valuesYaml);
    
    			// Collect all properties recursively
    			const allProperties = collectPropertiesRecursive(parsedYaml, "", doc);
    
    			// Set up Fuse.js for fuzzy searching
    			const fuse = new Fuse(allProperties, {
    				keys: ["propertyName", "propertyPath", "comment", "value"],
    				includeScore: true,
    				threshold: 0.4,
    			});
    
    			// Perform the fuzzy search
    			const searchResults = fuse.search(searchQuery);
    
    			// Format the results
    			let responseText = "";
    			if (searchResults.length > 0) {
    				responseText = `# Found ${searchResults.length} matching properties:\n\n`;
    
    				searchResults.forEach((result, index) => {
    					const property = result.item;
    					responseText += `## ${index + 1}. ${property.propertyPath}\n`;
    
    					if (property.comment) {
    						responseText += `Comment: ${property.comment.trim()}\n`;
    					}
    
    					if (property.value !== undefined) {
    						responseText += `Value: ${
    							typeof property.value === "object"
    								? JSON.stringify(property.value, null, 2)
    								: String(property.value)
    						}\n`;
    					} else {
    						responseText += "Value: [object]\n";
    					}
    
    					responseText += "\n";
    				});
    			} else {
    				responseText = `No properties matching "${searchQuery}" found.`;
    			}
    
    			return {
    				content: [
    					{
    						type: "text",
    						text: responseText,
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Error performing fuzzy search: ${
    							(error as Error).message
    						}`,
    					},
    				],
    			};
    		}
    	}
    );
  • The registration of the tool "helm-chart-values-fuzzy-search" with its schema definition using Zod.
    return server.tool(
    	"helm-chart-values-fuzzy-search",
    	"Fuzzy search through all properties/values/comments in a Helm chart's values.yaml file",
    	{
    		chartRepo: z.string().describe("The Helm chart repository name"),
    		chartName: z.string().describe("The Helm chart name"),
    		searchQuery: z.string().describe("The search query for fuzzy matching"),
    		version: z
    			.string()
    			.optional()
    			.describe("The chart version (optional, defaults to latest)"),
    	},
  • Helper function to recursively collect properties and comments from a YAML object.
    function collectPropertiesRecursive(
    	obj: any,
    	currentPath = "",
    	doc: any,
    	result: ValueProperty[] = []
    ): ValueProperty[] {
    	if (obj === null || typeof obj !== "object") {
    		return result;
    	}
    
    	for (const key in obj) {
    		const value = obj[key];
    		const newPath = currentPath ? `${currentPath}.${key}` : key;
    
    		// Try to extract comment for this property
    		let comment: string | undefined = undefined;
    		try {
    			// Navigate through the document to find comments
    			let currentNode = doc.contents;
    			for (const part of newPath.split(".")) {
    				if (
    					currentNode &&
    					typeof currentNode === "object" &&
    					"get" in currentNode
    				) {
    					const node = currentNode.get(part);
    					if (node) {
    						if (node.commentBefore) {
    							comment = node.commentBefore;
    						}
    						currentNode = node;
    					} else {
    						break;
    					}
    				} else {
    					break;
    				}
    			}
    		} catch (e) {
    			// If we can't get comments, just ignore and continue
    		}
    
    		// Add property to result
    		const property: ValueProperty = {
    			propertyName: key,
    			propertyPath: newPath,
    			comment,
    		};
    
    		// Only add value if it's not an object
    		if (value === null || typeof value !== "object") {
    			property.value = value;
    		}
    
    		result.push(property);
    
    		// Recursively process nested objects
    		if (value !== null && typeof value === "object") {
    			collectPropertiesRecursive(value, newPath, doc, result);
    		}
    	}
    
    	return result;
    }
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 context. It doesn't disclose what 'fuzzy search' entails (e.g., case sensitivity, matching algorithm), what the output format looks like, whether it's a read-only operation, or any rate limits/permissions needed. The description states the basic function but lacks operational details.

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 immediately conveys the core functionality. Every word earns its place with no redundant phrases or unnecessary elaboration. It's appropriately sized for a search tool with well-documented parameters.

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 search tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'fuzzy search' means operationally, what the return structure looks like, or how results are presented. The agent must guess about output format and search behavior, which is inadequate given the tool's complexity.

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%, providing clear documentation for all parameters. The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline of 3. It doesn't explain relationships between parameters (e.g., how chartRepo and chartName combine to identify a chart) or provide examples of searchQuery syntax.

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 specific action ('fuzzy search') and target resource ('properties/values/comments in a Helm chart's values.yaml file'), distinguishing it from sibling tools like 'helm-chart-values' (likely retrieves values) and 'helm-chart-templates-fuzzy-search' (searches templates). It uses precise terminology that aligns with Helm ecosystem concepts.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'helm-chart-values' (which might retrieve the entire values file) or 'helm-chart-templates-fuzzy-search' (which searches templates instead of values), leaving the agent to infer usage context from tool names alone.

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