Skip to main content
Glama

Render chart template

render_chart_template
Read-only

Render a chart version's Kubernetes manifests server-side, like helm template, with optional value overrides (the twin of ankra charts template) - no cluster connection, nothing is installed. Use this to show what an addon would deploy, to check that values produce the intended resources, or to find image references before installing. 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": "render_chart_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoNamespace for the render (default 'default').
chart_nameYesThe chart's name in that registry.
values_yamlNoOptional values YAML overriding the chart defaults (at most 512 KiB).
release_nameNoRelease name for the render (default: the chart name).
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description goes further by promising no cluster connection and nothing installed, which is the key safety fact for a render tool. It restates 'Read-only' redundantly, yet the server-side/no-cluster framing adds genuine behavioral context beyond the annotation.

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?

A single front-loaded sentence carries purpose, analogue, and use cases, and the trailing 'Read-only.' is a quick scannable flag. Minor waste exists in the parenthetical twin reference and the redundant read-only restatement, but nothing is bloated.

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 six parameters, a 100% covered schema, and annotations, the description covers purpose, safety, and use cases well. Since there is no output schema, one gap remains: it never says what the rendered result looks like (raw multi-document YAML vs. per-resource listing) or how large it may be, which an agent would want before calling.

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 all six parameters are already documented, including the 512 KiB values limit and default release/namespace behavior. The description only alludes to 'optional value overrides' and adds no syntax, formatting, or edge-case guidance beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource — rendering a chart version's Kubernetes manifests server-side — and anchors it with a familiar analogue (`helm template`). It also clarifies the output nature (manifests) and what it is not (a deploy), so an agent can distinguish it from install/apply siblings without reading the schema.

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 three concrete use cases (preview what an addon deploys, validate that values produce intended resources, extract image references before installing), which is stronger than most. It stops short of naming alternatives such as get_chart_default_values, deploy_inspect_chart_values, or cicd_validate_chart_values, leaving the agent to infer routing among near-neighbors.

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.