Skip to main content
Glama

Get backup posture

get_backup_posture
Read-only

Answer whether data is protected, and if not why not (the twin of the Backups posture the portal renders). scope=organisation is the fleet rollup with the vault counts, scope=cluster adds every stack on one cluster, scope=stack is one stack's protection state, schedule, vault, data asset counts, last restore point and failing runs in the last 24 hours. protection_state is protected, unprotected or unknown - unknown means Ankra could not establish it, NOT that the stack is unprotected. protected says a policy is declared, NOT that copies are being taken: a refused scheduled backup writes no run, so failing_runs_24h stays 0 and next_scheduled_at keeps moving. not_capturing with its reason and action, stale with its reason, and last_complete_restore_point_at null are what say no restore point is being taken or none ever completed; report those, never call such a stack backed up. Read-only. Only offered when backups are enabled for the organisation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_backup_posture"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoWhich question to answer. Omit to derive it: a stack_name means the stack, a named or selected cluster means that cluster, neither means the whole organisation. Pass organisation explicitly to get the fleet answer from inside a cluster-bound conversation.
cluster_idNoUUID of the cluster. Alternative to cluster_name.
stack_nameNoStack to report on, for scope=stack.
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

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, and the description adds a large amount of interpretive behavior beyond that: unknown means Ankra could not establish state, protected only means a policy is declared, refused scheduled backups leave failing_runs_24h at 0 while next_scheduled_at keeps moving. It also prescribes what to report (not_capturing, stale, null last_complete_restore_point_at) and explicitly forbids calling such a stack backed up.

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?

The highest-value content — the protection-state caveats — is front-loaded and every sentence carries operational meaning. The prose is very dense with several clauses chained by commas, which makes it slower to parse than it needs to be, but nothing is filler.

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

Completeness5/5

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

With no output schema, the description must convey what comes back, and it lists vault counts, data asset counts, protection state, schedule, last restore point and failing runs in 24 hours, plus the interpretation rules for each. The availability prerequisite is also stated, leaving nothing an agent needs missing.

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 schema already documents each parameter, but the description still adds semantics the schema does not: it labels scope as 'which question to answer' and spells out what each enum value returns. Cluster and stack parameters are not further elaborated, so it falls short of a 5.

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?

The description opens with a specific question it answers — whether data is protected and why not — and ties itself to the portal's Backups posture, which distinguishes it from sibling tools like get_backup_vault or list_restore_points that expose raw backup objects rather than a protection verdict.

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?

Each scope value is given an explicit meaning (fleet rollup with vault counts, all stacks on one cluster, single stack's state) and the final sentence states a hard prerequisite: only offered when backups are enabled for the organisation. It does not name an alternative tool for the case where the caller wants raw vault or restore-point data, so routing to siblings is left implicit.

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.