Skip to main content
Glama

Create stack profile

create_stack_profile
Destructive

Save a deployed stack on the current cluster as a NEW reusable stack profile (versioned template) that can be instantiated on any cluster in the organisation. Secret values are automatically redacted into parameters. Use when the user wants to reuse a stack elsewhere or turn it into a template. To add a new version to an EXISTING profile use save_stack_profile_version instead.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new profile. Must be unique within the organisation.
tagsNoTags for discovery.
categoryNoProfile category (e.g. 'monitoring', 'database').general
changelogNoChangelog entry for the initial version.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the deployed stack on this cluster to snapshot.
descriptionNoWhat this profile deploys and when to use it.
include_addon_configurationsNoInclude the stack's Helm values in the profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/side-effect profile is known; the description adds real value beyond that by disclosing that secret values are automatically redacted into parameters and that the resulting profile is instantiable org-wide. It does not explain why the operation is flagged destructive (e.g. whether the source stack is modified, or whether it fails when the name collides), which is the main remaining gap.

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?

Three sentences, front-loaded with the action and artifact, followed by side-effect disclosure and then the sibling disambiguation. No filler or restated title text.

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 an 8-parameter mutation with no output schema, the description covers purpose, trigger, reuse scope and the redaction side effect, which is most of what an agent needs. It stops short of saying what is returned (e.g. the new profile identifier) or any permission/ownership prerequisites, which would complete it.

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% with per-parameter descriptions for name, stack_name, cluster_id, tags, category, changelog, description and include_addon_configurations, so the schema carries the load. The description adds only peripheral meaning ('current cluster' anchoring cluster_id, 'NEW' implying name uniqueness must hold), which is a baseline 3.

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+resource with scope: 'Save a deployed stack on the current cluster as a NEW reusable stack profile (versioned template)'. The parenthetical clarifies the artifact type, and the final sentence separates it from save_stack_profile_version, so an agent can distinguish it from siblings without opening schemas.

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?

Gives explicit trigger conditions ('when the user wants to reuse a stack elsewhere or turn it into a template') and an explicit exclusion routing to an alternative ('to add a new version to an EXISTING profile use save_stack_profile_version instead'). Nothing is left to inference.

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.