Skip to main content
Glama

List database backups

databaseBackups
Read-onlyIdempotent

List the daily backups Tofu keeps of one owned app’s running managed database: one a day, kept for seven days, newest first, each with takenAt (UTC), status and restorable (only a completed backup can be gone back to). restore.requestable reports eligibility for a backup-restore request; when it would not, restore.code and restore.message contain a human-readable explanation. available: false means there is no list — no database, a database that is not running, or a read that failed (unavailable, which says nothing about whether backups exist). It reads no data, returns no credential and changes nothing. The dashboard’s Database page shows the same list under Backups, with Ask for a restore beside each complete copy, with the same recorded backups. One app per call, and a projectId the caller does not own is refused without saying anything about it.

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": {
      "projectId": "<projectId>"
    },
    "name": "databaseBackups"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
atYes
codeYes
backupsYes
messageYes
restoreYes
newestAtYes
availableYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations it discloses real behavior: seven-day retention, one-per-day, newest-first ordering, the `takenAt`/`status`/`restorable` shape, and the `restore.code`/`restore.message` explanation path. It also explains that `available: false` conflates no database, a stopped database, and a failed read, and that `unavailable` says nothing about backup existence — a genuinely useful caveat. Minor redundancy with annotations in 'reads no data ... changes nothing', plus an unaddressed auth/permission model beyond 'a projectId the caller does not own is refused'.

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 the purpose and dense with substantive detail rather than filler. The closing dashboard sentence and the repeated 'One app per call' restate ground already covered, and 'It reads no data, returns no credential and changes nothing' partly duplicates the annotations, but nothing is seriously wasteful.

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 single-parameter read with an output schema and full annotations, this covers nearly everything an agent needs: what is returned, ordering, retention, the empty/failed cases, and restore eligibility. The only gaps are the absence of an explicit pointer to the restore-request sibling and no guidance on sourcing a valid projectId.

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?

With only one parameter at 0% schema description coverage, the description carries the load, and it does add meaning: it ties projectId to a single owned app and warns that a non-owned projectId is refused without disclosing anything about it. It still never states the projectId format or where to obtain one, so the compensation is partial.

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?

States a specific verb and resource with scope: 'List the daily backups Tofu keeps of one owned app's running managed database.' It also pins the scope to one app per call and one projectId, which distinguishes it from sibling reads like databaseStatus and from mutation siblings like databaseRestore/databaseRestoreRequest.

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 rather than stated: the reader infers this is the pre-check for a restore because 'restorable' and 'restore.requestable' are documented, but the definition never names databaseRestoreRequest or databaseRestore as the follow-up tool, nor says when not to call this. The dashboard analogy gives context but no explicit routing rule.

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.

Resources