Skip to main content
Glama

Protect stack

protect_stack
Destructive

Turn on scheduled backup protection for a stack (the twin of ankra cluster stacks protect): Ankra writes the stack's backup policy through GitOps and the ankra-backup stack on the cluster takes the captures. Omitted fields keep the stack's stored policy, so a schedule change need not restate the selection. Setting databases=false means the restore points carry NO database contents, which needs confirm_exclude_databases=true. 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>"
    },
    "name": "protect_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheduleNohourly, daily, weekly, or a cron expression. Omit to take the platform default (daily).
vault_idNoBackup vault id or name to write to, from list_backup_vaults. Omit when the organisation has exactly one ready vault.
databasesNoWhether the stack's databases are captured. Setting it to false means the restore points carry no database contents at all. Naming it at all makes the selection explicit, so pair it with persistent_volume_claims unless you mean to capture the databases alone.
retentionNoHow many restore points each tier keeps. Omit to take the platform default.
backup_nowNoAlso take a restore point immediately, rather than waiting for the first scheduled run.
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameYesThe stack to protect.
cluster_nameNoExact name of the cluster. Optional when a cluster is already selected in the conversation.
persistent_volume_claimsNoNames of the persistent volume claims to capture, from list_stack_data_assets. A selection is applied WHOLE, not merged with the stack's stored one: naming none of them captures no volumes at all. Send no selection (no databases, no persistent_volume_claims) to keep the stack's stored policy.
confirm_exclude_databasesNoRequired with databases=false: acknowledges that this stack's restore points will carry no database contents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only say destructiveHint=true, readOnlyHint=false, idempotentHint=false; the description adds the actual mechanism (policy written through GitOps, captures performed by the ankra-backup stack), the partial-update semantics (omitted fields preserve stored policy), the destructive edge case (databases=false yields restore points with NO database contents), and the required `backups.manage` permission. That is materially more than the annotations convey.

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?

Dense but front-loaded: the purpose leads, followed by mechanism, then the omission and exclusion caveats. The parenthetical CLI-twin reference is somewhat incidental but useful for cross-referencing; otherwise every sentence carries information.

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 10-parameter mutation tool with a nested retention object and no output schema, the description covers the highest-risk behaviors (permission, destructive exclusion, partial-update semantics) adequately. It is silent on what happens on a repeat call and on how confirmation is reported back, which the absent output schema leaves unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema cannot express: omission preserves stored policy, and databases=false is gated by confirm_exclude_databases=true. It does not elaborate on schedule/vault/retention formats, which the schema already covers.

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 precise verb and resource — turning on scheduled backup protection for a stack — and explains the mechanism (Ankra writes the backup policy via GitOps, the ankra-backup stack takes captures). It is clear what the tool does, but it never distinguishes itself from sibling operations such as create_stack_restore_point or the backup_now flag embedded in its own schema, so an agent must infer the boundary.

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?

Gives concrete usage context: it is the twin of `ankra cluster stacks protect`, omitted fields keep the stored policy (so a schedule tweak need not restate the selection), and databases=false requires confirm_exclude_databases=true. It does not name any sibling alternative or state a when-not-to-use case, which keeps it below a 5.

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.