Skip to main content
Glama

Get chart default values

get_chart_default_values
Read-only

The default values.yaml of one chart version (the twin of ankra charts values), as the chart ships it. Use this before writing an addon configuration or to explain what a chart does by default; a stack addon's configuration overrides these. Read-only.

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": {
      "registry_name": "<registry_name>",
      "chart_name": "<chart_name>",
      "chart_version": "<chart_version>"
    },
    "name": "get_chart_default_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_nameYesThe chart's name in that registry.
chart_versionYesThe exact chart version (from list_chart_versions).
registry_nameYesThe Helm registry's name in Ankra (from list_helm_registries).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine context beyond that: the values are the pristine chart-shipped defaults, not the effective configuration, and addon configuration overrides them. That semantic distinction is the main thing an agent needs to know.

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?

Two tight sentences plus a one-word safety tag. The core identity of the resource comes first, followed by usage and precedence, with no redundant restatement of the name or schema.

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?

There is no output schema, but the description makes clear the return is the chart's shipped values.yaml, which is sufficient for a read-only lookup with fully documented parameters. Only the exact response shape (raw YAML vs parsed object) is left implicit.

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% and all three parameters are documented in the schema, including provenance hints (from list_chart_versions, from list_helm_registries). The description adds nothing per-parameter, so the baseline 3 applies.

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?

States a specific verb and resource: retrieve the default values.yaml for one chart version, with a concrete referent ('the twin of `ankra charts values`') and the qualifier 'as the chart ships it'. That distinguishes it from get_chart_details and render_chart_template, though it never names those siblings explicitly.

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?

Gives explicit when-to-use guidance: before writing an addon configuration, or to explain default chart behavior, plus the precedence rule that a stack addon's configuration overrides these values. It stops short of naming when-not-to-use or pointing at a specific sibling for merged/rendered values.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.