Skip to main content
Glama

Get application backups

get_application_backups
Read-only

Read an Application's Backups section: whether it has a database, whether a deploy arms the database-backup default, and for each deployment its cluster, stack and backup posture (protection state, schedule, last restore point, why it is not protected). ready_vault_count with ready_vault_known says whether the organisation has a verified backup vault at all. Each deployment's keeping is what its backups keep, as the Backups page shows it. Read keeping.state first (known, no_policy or unknown); with unknown every fact is null, and null there never means none. keeps_days and keeps_everything are the policy; kept_count and oldest_kept_at are what is kept now; protected_since and last_restore_test are set only when their own _state is known. keeping is null until the deployment has a stack. A deployment's restore points are read with list_restore_points on its cluster and stack. Read-only; needs backups.read.

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": {
      "application_id": "<application_id>"
    },
    "name": "get_application_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the required scope ("needs backups.read") and valuable null semantics ("with unknown every fact is null, and null there never means none") plus the prerequisite that keeping is null until a stack exists. These are genuinely useful behavioral disclosures beyond the annotation, though return shape and size are left implicit.

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?

Front-loaded with purpose and payload scope, then field semantics, then the sibling route and auth requirement. Dense but each sentence carries distinct information; the field-by-field walkthrough is long but justified because no output schema exists.

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 carries the full burden of explaining return values and does so thoroughly: field groups, the known/no_policy/unknown state machine, which fields are conditional on their own _state, and the null-vs-none distinction. An agent can interpret the response without guessing.

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?

There is a single parameter with 100% schema description coverage, so the schema already fully documents application_id. The description adds nothing about the identifier's format or sourcing, 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?

"Read an Application's Backups section" gives a specific verb and resource, then enumerates the exact payload: database presence, deploy-armed default, and per-deployment cluster/stack/backup posture. It partially differentiates from siblings by routing restore points to list_restore_points, but it does not distinguish itself from adjacent get_application_* readers such as get_application_deployments.

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?

It names an explicit alternative with a condition: restore points are read via list_restore_points on the deployment's cluster and stack, which prevents an agent from expecting that data here. It also gives a consumption rule ("Read keeping.state first"), but never states when this tool should not be used or what prerequisites must exist 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.