Skip to main content
Glama

backup_list

Read-onlyIdempotent

The backup jobs and recent archives of one of the user's servers: what each job covers (folders and databases), when it ran, whether it succeeded, how big it is and where it is stored; drafts waiting for the owner's confirmation are marked DRAFT with their confirmation link; also the storage the owner set up (names usable as backup_job_create's destination). Use it to check that a backup exists before a risky change, or to see whether last night's backup worked.

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": {
      "host": "<host>"
    },
    "name": "backup_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesServer id or exact name from hosts_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful disclosure beyond that: drafts appear as DRAFT with a confirmation link, size and storage location are included, and storage names are reusable as backup_job_create destinations.

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?

Two sentences, front-loaded with the resource and contents, followed by usage. The first sentence is dense with semicolon-separated clauses but each clause carries real information about return contents.

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 burden of explaining return values and does so thoroughly: coverage, run time, success, size, storage, and DRAFT markings. An agent knows what it will get back and what it can do with the storage names.

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% with a single documented host parameter ('Server id or exact name from hosts_list'), so the schema does the work. The description only reinforces that the scope is one user's server and adds no syntax or format detail beyond the schema; baseline 3 applies.

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 resource (backup jobs and recent archives) scoped to one server, and enumerates what each record contains. It implicitly separates itself from the write-side siblings (backup_create, backup_job_create) by framing storage names as destinations those tools can use, though it never names an alternative read tool explicitly.

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 two concrete use cases: verifying a backup exists before a risky change, and checking whether last night's backup succeeded. It does not state when to prefer a different tool (e.g. job_list/job_status) or any exclusions, so it stops short of full routing guidance.

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.