Skip to main content
Glama

Helm MCP

by io.github.Kubedoll-Heavy-Industries

get_values

Read-only

Get chart values.yaml with optional JSON schema. Uses depth limiting (default 2) to show structure without overwhelming context. Use path to drill into specific sections, depth=0 for full YAML. include_examples surfaces nearby commented YAML examples and requires path to be set. Supports both HTTP/HTTPS repos and OCI registries (oci://).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoYAML path (e.g. .ingress.enabled)
depthNoMax nesting depth (default 2, 0 for unlimited)
chart_nameYesChart name (e.g. postgresql)
chart_versionNoChart version (defaults to latest)
example_limitNoMaximum nearby examples to include (default 1, max 3, 0 falls back to default)
show_commentsNoPreserve YAML comments
show_defaultsNoInclude default values
include_schemaNoInclude values.schema.json in response
repository_urlYesHelm repository URL (e.g. https://charts.bitnami.com/bitnami) or OCI registry (e.g. oci://ghcr.io/traefik/helm)
max_array_itemsNoMax array items before truncation (default 3, 0 for unlimited)
include_examplesNoInclude nearby commented YAML examples for the selected path (requires path to be set)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoExtracted path, if specified
schemaNoJSON Schema for values (if include_schema=true and schema exists)
valuesYesValues content (YAML)
versionYesResolved chart version (especially useful when chart_version was omitted and latest was used)
examplesNoNearby commented YAML examples, if include_examples=true and examples are found
parse_warningNoSet when the YAML parser failed on this chart's values.yaml. The 'values' field then contains raw bytes (possibly truncated) and path/depth/include_examples/include_schema were not applied
schema_warningNoSet when include_schema=true but the schema could not be retrieved; absence of this field with empty schema means the chart has no schema

TDQS

A4.4/5.0
Behavior4/5

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

Adds value beyond annotations by disclosing depth limiting defaults, the meaning of depth=0, include_examples behavior, and OCI registry support. No contradiction with readOnlyHint/openWorldHint, and the read-only safety is already surfaced by annotations.

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?

Three concise, front-loaded sentences. The core purpose appears first, followed by operational guidance and registry support. No filler, repetition, or vague prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool, the description plus annotations, 100% schema coverage, and output schema make this largely complete. It provides the key behavioral caveats around depth and include_examples; the main gap is not naming sibling alternatives for other chart metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is already strong. The description adds useful context for depth, path, and repository_url including OCI behavior, while leaving other fields to the schema.

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 an exact resource: chart values.yaml, with optional inclusion of values.schema.json. This is sharply distinct from siblings like get_dependencies, get_notes, get_versions, and search_charts.

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

Usage Guidelines4/5

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

Provides concrete usage guidance: use path for drilling, depth=0 for full YAML, and include_examples requires path. It does not explicitly list sibling alternatives for cases such as fetching versions or dependencies, but the in-tool guidance is strong.

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

All Helm MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool serves a distinct purpose: search_charts finds charts, get_versions lists versions, get_values retrieves configuration, get_notes provides post-install instructions, and get_dependencies exposes sub-charts. No overlapping functionality; boundaries are clear even for similar tasks.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_dependencies, get_notes, get_values, get_versions, and search_charts. This makes the tool set predictable and easy to navigate.

Tool Count5/5

With 5 tools, the set is well-scoped for inspecting Helm charts. Each tool addresses a significant aspect of chart discovery and inspection, and none feel redundant or extraneous.

Completeness5/5

The tool surface covers the full range of chart inspection tasks: searching repositories, checking versions, retrieving values, viewing notes, and revealing dependencies. No obvious gaps for a read-only inspection server.

Resources