Skip to main content
Glama

Delete stack

delete_stack
Destructive

Delete an entire stack and all its addons/manifests from the cluster. This is a destructive operation.

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

Input Schema

NameRequiredDescriptionDefault
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
stack_nameYesName of the stack to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, so 'This is a destructive operation' largely repeats structured data. The one genuinely additive fact is the cascade — that addons and manifests belonging to the stack are removed too — but the description says nothing about reversibility, required permissions, or whether workloads keep running after the stack record is gone.

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?

Two short sentences, front-loaded with the action and its scope. The second sentence is redundant against the destructiveHint annotation, so it doesn't fully earn its place, but there is no bloat overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with no output schema, the description covers what is destroyed but omits preconditions (protection state, confirmation steps) and the post-deletion state of the cluster. Annotations handle the safety profile, so the gaps are modest rather than critical.

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 cluster_id documenting UUID discovery via list_clusters and stack_name defined inline, so the schema carries the load. The description adds no parameter-level meaning, which is acceptable at this coverage level but earns only the baseline.

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?

States a specific verb ('Delete') and resource ('an entire stack') and adds scope detail that the name alone doesn't convey: the addons and manifests belonging to the stack go with it. It does not distinguish itself from nearby siblings such as delete_stack_profile, uninstall_addon_from_stack, or protect_stack/unprotect_stack, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g. whether the stack must be unprotected first), and no pointer to alternatives for a narrower teardown. Usage is only inferable from the tool name.

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.