Skip to main content
Glama

Deploy inspect chart values

deploy_inspect_chart_values
Read-only

Probe a Helm chart's values.yaml for the canonical paths Ankra's deploy-wizard cares about (ingress.enabled, ingress hosts/class, env, envFrom, image.repository) and shallow concept flags (default ingress.enabled, default service.port). Pass the raw values.yaml content as 'content'. Use this once per analysis to populate the DeployAnalysis.chart_values_shape field - when a path comes back as null the wizard tells the user the chart uses non-standard keys instead of silently miswriting.

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": {
      "content": "<content>",
      "cluster_id": "<cluster_id>"
    },
    "name": "deploy_inspect_chart_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesFull values.yaml content of the application's chart.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 genuinely new behavioral context, namely that null results signal non-standard keys and that the wizard then warns the user rather than miswriting. With no output schema, it also sketches what comes back (path values plus shallow concept flags), though the exact return shape is only implied.

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 purpose and followed by the usage rule, with no filler. Minor cost: the phrase 'shallow concept flags' is jargon that adds ambiguity rather than precision.

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 a two-parameter read-only probe with no output schema, the description covers what is inspected, how to call it, and what a null result means. The one real gap is that the return structure is only partly described, so the agent must infer the response shape.

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 coverage is 100%, so both parameters are already documented in the schema. The description adds only a modest clarification that 'content' should be the raw values.yaml text rather than a parsed object, and says nothing about cluster_id beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 ('probe') and resource (a Helm chart's values.yaml) and enumerates the exact paths inspected (ingress.enabled, ingress hosts/class, env, envFrom, image.repository) plus shallow flags, so the agent knows precisely what the tool extracts. It does not, however, distinguish itself from near-siblings like get_chart_default_values, cicd_validate_chart_values, or render_chart_template, which an agent could easily confuse it with.

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 gives a clear usage rule: 'Use this once per analysis to populate the DeployAnalysis.chart_values_shape field', which tells the agent the frequency and the downstream consumer. It stops short of naming alternatives or stating when NOT to use it (e.g. when values are already known or when a chart is not Helm-based).

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.