Skip to main content
Glama

Instantiate stack profile

instantiate_stack_profile
Destructive

Create a stack DRAFT from a stack profile - on the current cluster, or on another cluster in this organisation via target_cluster_id (the 'move this stack to cluster X' flow: snapshot with create_stack_profile, then instantiate on the target). Nothing is deployed: the result is a saved draft visible on that cluster's Stacks page. A cross-cluster target requires the user to hold ai.execute and stacks.write on the target cluster, and the target must be confirmed with the user before calling (list_clusters shows the candidates). Required parameters (from get_stack_profile) must be provided as name/value pairs. For secret-type parameters, NEVER pass or ask for a raw secret value - pass a ${SECRET_SLOT:} sentinel from the user's slot catalog; the sentinel is stored at the declared encrypted path in the draft and resolved from Vault only when the stack deploys, so the value never appears in the draft or this chat. A missing or expired slot fails the call. If the user has no slot, tell them to instantiate from the portal where the value can be entered securely. Raw secret-looking values are rejected. After instantiating on the current cluster, load the draft with load_draft_from_database to review or edit it, and only deploy via apply_stack_changes when the user asks. A cross-cluster draft is reviewed and applied on the target cluster - this session cannot deploy there.

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

Input Schema

NameRequiredDescriptionDefault
versionNoProfile version to instantiate. Defaults to the profile's current version (the pinned version, which can be older than latest after a rollback).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
parametersNoValues for the profile's parameters. Required parameters must all be provided.
profile_idNoUUID of the profile to instantiate. Alternative to profile_name.
profile_nameNoName of the profile to instantiate. Alternative to profile_id.
new_stack_nameNoName for the new stack. Defaults to the profile's stack name; auto-renamed on conflict.
target_cluster_idNoOptional UUID of another cluster in the organisation to create the draft on. Defaults to the current cluster. Requires ai.execute and stacks.write on the target cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=true, idempotent=false) by disclosing the actual side effect: no deployment occurs, the output is a saved draft visible on the target cluster's Stacks page. It adds authorization requirements (ai.execute and stacks.write on the target), a confirmation prerequisite with the user, and concrete failure modes (missing or expired slot, rejected raw secret-looking values).

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?

The purpose and the "nothing is deployed" clarification are front-loaded, and nearly every sentence carries distinct operational information. The single dense paragraph does pack several independent concerns (auth, secrets, follow-up steps, cross-cluster limits), which makes it heavy to parse but not padded.

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?

For a 7-parameter write tool with no output schema, the description covers outcome, permissions, user-confirmation requirement, secret-handling policy, failure conditions, and the full follow-up lifecycle including the cross-cluster limitation. An agent has enough to call this correctly or to tell the user why it cannot.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3; the description still adds value schema cannot, notably the ${SECRET_SLOT:<slot-id>} sentinel syntax for secret-type parameter values and the rule that required parameters come from get_stack_profile as name/value pairs. It also frames target_cluster_id as the "move this stack to cluster X" flow, which the schema only describes mechanically.

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?

"Create a stack DRAFT from a stack profile" names a specific verb and resource, and immediately scopes it against the two siblings an agent could confuse it with: create_stack_profile (produces the profile) and apply_stack_changes (deploys). The cross-cluster variant is stated as a distinct flow via target_cluster_id.

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 routing: get_stack_profile for required parameters, list_clusters for target candidates, load_draft_from_database to review or edit after instantiating, apply_stack_changes only when the user asks to deploy. It also states the when-not: this session cannot deploy a cross-cluster draft, and the portal is the fallback when no secret slot exists.

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.