Skip to main content
Glama

Delete stack profile

delete_stack_profile
Destructive

Delete a stack profile and all its versions from the organisation's catalog. Stacks already instantiated from the profile keep running - only the template is removed. This cannot be undone from chat.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
profile_idNoUUID of the profile to delete. Alternative to profile_name.
profile_nameNoName of the profile to delete. Alternative to profile_id.

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?

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: cascade to all versions, no impact on instantiated stacks, and irreversibility specifically from chat, which hints at an out-of-band recovery path.

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 short sentences, front-loaded with the action and scope, followed by the blast-radius clarification and the irreversibility warning. Nothing is redundant or padded.

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 a destructive, three-parameter tool with an output schema absent and annotations covering the safety profile, the description supplies the essential blast radius and reversibility information. It could go slightly further by noting what happens if the profile is referenced by drafts or whether cluster scoping limits which profiles can be deleted.

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 coverage is 100%, and the schema itself documents cluster_id, profile_id, and profile_name including the id/name alternative. The description adds no additional meaning about these parameters, so baseline 3 applies.

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 ("Delete a stack profile") and adds critical scope: all its versions, from the organisation's catalog. The clarifying sentence that instantiated stacks keep running separates it cleanly from delete_stack, which an agent could otherwise confuse it with.

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

Usage Guidelines3/5

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

The description implies the usage context (removing a template, not instances) by stating that running stacks survive, which is helpful disambiguation. However, it never names alternatives such as delete_stack, update_stack_profile, or unpublish-related tools, nor does it state preconditions like whether the profile must be unpublished first.

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.