Skip to main content
Glama

Validate stack

validate_stack
Read-only

Validate a stack specification against the cluster without creating or deploying anything: replays the same validation the create lane runs (duplicate stack name, member shape, chart and dependency checks) and reports the errors. The stack object uses the same shape as create_stack, including the parents dependency edges. Returns {valid, errors}, plus a dependency_review whenever a multi-member specification declares no parents at all - those members would deploy in parallel and race each other. Use this before create_stack, and add the missing parents before deploying. 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": {
      "stack": "<stack>",
      "cluster_id": "<cluster_id>"
    },
    "name": "validate_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackYesThe stack specification to validate - the same shape create_stack accepts, including each member's parents.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / stack / properties / addons / items / properties / configuration / properties / encrypted_paths / description
      Added value: +"Extra keys to seal with SOPS when the stack is committed to GitOps, e.g. \"stringData.password\" or \"auth.password\" (sops matches the last key name at any depth). A key holding a ${SECRET_SLOT:<id>} sentinel is sealed automatically and needs no entry; list a key here only to seal a value that is not a sentinel."
    • addedInput schema / properties / stack / properties / manifests / items / properties / encrypted_paths / description
      Added value: +"Extra keys to seal with SOPS when the stack is committed to GitOps, e.g. \"stringData.password\" or \"auth.password\" (sops matches the last key name at any depth). A key holding a ${SECRET_SLOT:<id>} sentinel is sealed automatically and needs no entry; list a key here only to seal a value that is not a sentinel."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotation, it discloses what the validation actually replays, that nothing is created or deployed, the return shape {valid, errors}, and the non-obvious dependency_review behavior when a multi-member spec declares no parents. That race-condition warning is real behavioral context an agent could not infer elsewhere.

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?

Front-loaded with the core action and the 'without creating or deploying' constraint, and each sentence carries distinct information (checks, payload shape, return, usage). It is on the long side at five sentences, but little is redundant apart from the trailing 'Read-only' restating the annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly supplies the return contract ({valid, errors} plus optional dependency_review). For a two-parameter read-only validation tool over a deeply nested spec, this covers everything an agent needs to invoke it and interpret results.

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 the nested stack shape and parents edges are already documented in the schema. The description only adds that the payload matches create_stack's shape, which the schema's stack description already says. Baseline 3 applies since the schema does the heavy lifting.

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 (validate a stack specification) plus explicit scope: it replays the create lane's validation against the cluster without creating or deploying anything. The enumerated checks (duplicate name, member shape, chart and dependency) make it unmistakable versus the many mutating stack siblings.

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 usage guidance: 'Use this before create_stack, and add the missing parents before deploying,' which names the alternative it precedes. It does not explicitly say when not to use it, and it does not differentiate from the similarly named validate_cluster_manifest sibling, which is the main gap.

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.