Skip to main content
Glama
artifacthub-mcp

artifacthub-mcp

by Ankur1911

chart_values

Read-onlyIdempotent

Inspect a Helm chart's default values.yaml without downloading the full file: return an outline of top-level keys or search lines with context and inline comments.

Instructions

Inspect a chart's default values.yaml without downloading all of it (they are often thousands of lines). Without search it returns an outline of top-level keys with line numbers. With search it returns matching lines with surrounding lines, which keeps the publisher's inline comments, e.g. search='persistence' or 'resources'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo": "<repo>",
      "name": "<name>"
    },
    "name": "chart_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoPackage kind; values files exist for 'helm' charts.helm
nameYesPackage name within the repository, e.g. 'postgresql'.
repoYesRepository name on Artifact Hub (the 'repo' value from search_packages), e.g. 'bitnami'.
searchNoCase-insensitive text to look for in values.yaml. Omit for the outline.
contextNoLines of context around each match.
versionNoExact version. Omit for the latest version.
max_linesNoMaximum lines to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds meaningful behavior beyond that: results are truncated (max_lines), an outline is returned without 'search', and inline publisher comments are preserved in search results — the last point is genuinely non-obvious and valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, then the two return modes. The parenthetical about thousands of lines earns its place by motivating the tool. Slightly dense but no filler.

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?

With seven parameters and no output schema, the description does the necessary work of describing return shape in both modes and the truncation cap. Things like version defaulting to latest are left to the schema, which is acceptable given full coverage.

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 3. The description still adds semantic value by illustrating what `search` should contain and by framing `context`/`max_lines` as the outline-vs-snippet and truncation controls, rather than just restating the schema.

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 uses a specific verb and resource — 'Inspect a chart's default values.yaml' — and immediately explains the value proposition (avoiding a thousands-of-line download). It does not name a sibling tool such as package_details to draw a boundary, so it falls just short of the top score.

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?

It clearly explains the two operating modes: omit 'search' for an outline of top-level keys, include 'search' for matching lines with context. It gives concrete example search terms ('persistence', 'resources'), which helps an agent decide which mode fits. It doesn't explicitly say when to prefer a different tool (e.g. package_details) instead.

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