Skip to main content
Glama

Create stack

create_stack
Destructive

Create and deploy a NEW stack on the cluster from a full specification of its addons and manifests. ALWAYS declare the deployment order with parents: a member with no parents deploys in PARALLEL with every other parentless member, so a chart that needs a namespace, a Secret, a ConfigMap, a CRD, an operator, or a database another member of the stack provides will race it and fail. A parent is {"name": "", "kind": "addon" or "manifest"}; kind is lowercase and must match the referenced member's type. Typical edges: the Namespace, Secret, and ConfigMap manifests are parents of the addons that consume them; cert-manager is a parent of its ClusterIssuer manifest; an operator addon is a parent of the custom-resource manifests it reconciles; a database addon is a parent of the application that connects to it. Leave a member parentless only when it is genuinely independent of every other member. Deployment starts immediately and the change is pushed to the cluster's GitOps repository when one is connected. NEVER pass raw secret values in values or manifests - use ${SECRET_SLOT:} sentinels from the user's slot catalog; raw secret-looking values are refused. Manifests carrying cluster-scoped or cluster-critical kinds (CustomResourceDefinition, ClusterRole, webhook configurations, PersistentVolume, ...), documents in protected namespaces (kube-, ankra-), or bindings to cluster-admin are refused by policy - manage those through the UI. Validate the specification with validate_stack first - it reports the members left with no dependency edges - and use update_stack for a stack that already exists.

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": "create_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackYesThe stack specification. Each member may carry agents_md - AGENTS.md markdown of operational learnings saved beside it in GitOps for future agents. Secret values must use ${SECRET_SLOT:<slot-id>} sentinels - raw secrets are refused.
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.6/5.0
Behavior4/5

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

Goes well beyond the supplied annotations: deployment starts immediately, the change is pushed to the connected GitOps repository, raw secrets are refused in favour of ${SECRET_SLOT} sentinels, and cluster-scoped/cluster-critical kinds, kube-*/ankra-* namespaces, and cluster-admin bindings are policy-refused. Combined with destructiveHint=true and idempotentHint=false, an agent understands this writes to the cluster and is not repeatable. It does not say what the call returns on success, which keeps it off a 5.

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?

Purpose is front-loaded in the first clause, and nearly every sentence carries load-bearing rules that cannot be removed without losing correctness. It is a single dense block with no bullets or line breaks, so the parent-ordering rules and the secret/policy rules are harder to scan than they need to be.

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?

Complete for a complex nested-spec creation tool: ordering semantics, secret handling, policy refusals, validation workflow and the update alternative are all covered. The only real gap is the absence of any statement about what a successful call returns or how to observe deployment progress, which matters for a tool that starts an asynchronous rollout.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3, but the description adds real meaning the schema does not: why parents matter (parentless members deploy in PARALLEL and race their dependencies), the exact shape of a parent {"name", "kind"}, that kind is lowercase and must match the referenced member's type, and that sentinels are required for secret values. That converts a structural schema into actionable semantics.

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 ("Create and deploy a NEW stack on the cluster from a full specification of its addons and manifests") and immediately differentiates itself from update_stack by scoping to new stacks. The capitalized NEW plus the closing instruction to use update_stack for existing stacks leaves no ambiguity about which sibling applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use and when-not-to-use: validate_stack first, update_stack for existing stacks, and a detailed rule for when a member may be left parentless ("only when it is genuinely independent of every other member"). It also names the concrete dependency patterns (namespace/secret/configmap before consumers, operator before CRs, database before app) that an agent needs in order to build a correct spec.

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.