Skip to main content
Glama

Unprotect stack

unprotect_stack
Destructive

Turn OFF scheduled backup protection for a stack (the twin of ankra cluster stacks unprotect). No new restore points are taken after this; restore points already taken are kept and stay restorable. confirm must be the stack's own name, typed exactly. Requires backups.manage.

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>",
      "confirm": "<confirm>"
    },
    "name": "unprotect_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesThe stack name, typed exactly, confirming that this stack stops being backed up.
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameYesThe stack to stop protecting.
cluster_nameNoExact name of the cluster. Optional when a cluster is already selected in the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, so the safety profile is covered. The description still adds real value: it clarifies that existing restore points are retained and remain restorable, and that the `backups.manage` permission is required — neither of which is in the structured fields.

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?

Four tight sentences, front-loaded with the action, followed by side effects, the confirmation constraint, and the permission. The CLI-twin parenthetical is the only marginally expendable element.

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 mutation with no output schema, the description covers effect, data retention, confirmation semantics, and authorization. Only the absence of any reversal path or prerequisite-state note keeps it from being fully complete.

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%, so all four parameters are already documented. The description's note that `confirm` must be the exact stack name largely repeats the schema text, though it emphasizes the typo-safety guard.

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 and resource ('Turn OFF scheduled backup protection for a stack') and the CLI twin, making the operation unambiguous. It does not explicitly name the inverse sibling `protect_stack`, but the direction of the action is unmistakable.

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?

Usage is implied: call this when a stack should stop being backed up. There is no explicit when-not guidance and no pointer to `protect_stack` as the reverse operation or to `get_backup_posture`/`list_restore_points` for inspection 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.