Skip to main content
Glama

Save stack profile version

save_stack_profile_version
Destructive

Snapshot a deployed stack on the current cluster as a NEW VERSION of an existing stack profile. Earlier versions are preserved and remain instantiable. Use when the user updated a stack and wants the profile to reflect the new state.

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_name": "<stack_name>",
      "cluster_id": "<cluster_id>"
    },
    "name": "save_stack_profile_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
changelogNoWhat changed in this version.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
profile_idNoUUID of the existing profile. Alternative to profile_name.
stack_nameYesName of the deployed stack on this cluster to snapshot.
profile_nameNoName of the existing profile to add a version to. Alternative to profile_id.
include_addon_configurationsNoInclude the stack's Helm values in the version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already disclose that this is a non-read-only, non-idempotent, destructive write. The description adds valuable context beyond that: the old versions are preserved and are still instantiable, which tells the agent that a new version is appended rather than overwritten. It stops short of stating permission requirements, whether the snapshot touches the live cluster, or what happens if the stack is out of sync with the profile.

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?

It is three short sentences: the core action first, then the versioning consequence, then the usage trigger. Each sentence carries new information, and there is no restatement of the title or padding.

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?

Six parameters, full schema coverage, and no output schema, so the description only needs to cover the action and its side effects. It does that well: it states what is created, what is retained, and when to use the tool. What is missing is secondary detail about permissions and whether the call requires the stack to be deployed and unchanged.

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 baseline is 3: the description adds no syntax or format detail for changelog, include_addon_configurations, or the profile_id/profile_name alternative. It also describes the target as 'the current cluster' even though cluster_id is a required parameter, which slightly understates that the cluster must be supplied explicitly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: it snapshots a deployed stack as a new version of an existing stack profile, and it clarifies what is created versus preserved. It does not explicitly distinguish itself from close siblings like update_stack_profile, create_stack_profile, or publish_stack_profile_draft, so the agent must infer which one applies.

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 says when to use the tool: the user updated a stack and wants the profile to reflect the new state. That is a clear triggering condition, but there is no when-not guidance, and no alternative is named for the case where the user has no existing profile or has only draft changes.

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.