Skip to main content
Glama

CI/CD validate chart values

cicd_validate_chart_values
Read-only

Validate a Helm chart values.yaml string against Ankra's Kubernetes security defaults (KSV-0014 readOnlyRootFilesystem, podSecurityContext.runAsNonRoot, capabilities.drop: [ALL], healthCheck.path). Use this on a customer's pre-existing chart values before suggesting changes. Returns severity and per-violation keys.

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>"
    },
    "name": "cicd_validate_chart_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesFull values.yaml content (typically read via github_read_file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a non-mutating check, and the description adds meaningful behavioral detail: the specific security defaults checked and the fact that the result includes severity and per-violation keys. It does not describe error handling or exact severity levels, but it adds useful 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.

Conciseness5/5

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

The description is two sentences with no filler: purpose and checks come first, followed by usage context and a brief return summary. Every sentence contributes information an agent needs.

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 simple one-parameter validation tool with a fully documented schema and no output schema, the description is mostly complete: it explains what is validated and summarizes the return shape. It could be slightly richer about severity values or validation limitations, but no critical information is missing.

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%, and the schema already explains that 'content' is full values.yaml content, typically read via github_read_file. The description reinforces that it is a values.yaml string but adds no new format, size, or syntax guidance beyond 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 uses a specific verb, 'Validate', and a precise resource, a Helm chart values.yaml string, plus names the exact security defaults being checked. This distinguishes it clearly from sibling validators such as cicd_validate_pipeline_yaml, cicd_validate_workflow_yaml, and validate_cluster_manifest.

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 clear when-to-use guidance: apply it to a customer's pre-existing chart values before suggesting changes. It does not name alternative tools or exclusions, so it falls short of the top mark, but the intended context is explicit.

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.