Skip to main content
Glama

backup_create

Destructive

Make an encrypted backup of one of the user's servers now, through Termalin's backup job for that server, and wait for it (up to about a minute; a longer one keeps running and shows up in backup_list). Call it BEFORE a risky change — a migration, a config rewrite, a bulk delete — and say so in 'label'. A job can hold folders and databases (PostgreSQL, MySQL/MariaDB, also inside a Docker container) — the archive then has a .sql dump of each. The server needs a confirmed backup job: if it has none, propose one with backup_job_create (it is a draft until the owner confirms it in the cabinet, which makes the encryption key); a draft can't be run. Uses the owner's storage quota, and keeps the job's 'keep last' count: when that many archives exist, the oldest one is removed.

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_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoName of the backup job when the server has several (default: the first)
hostYesServer id or exact name from hosts_list
labelNoWhy this backup is being made, e.g. 'before upgrading postgres'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the ~1 minute wait with longer runs continuing and appearing in backup_list, the prerequisite of a confirmed job, that it consumes the owner's storage quota, and that the job's retention count deletes the oldest archive once the limit is reached — directly explaining the destructiveHint=true annotation.

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-loads the action and the timing advice, then adds prerequisites and retention. Dense but each clause carries operational weight; the parenthetical about Docker/SQL dumps is slightly tangential but still informs what the archive contains.

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?

No output schema exists, so the description supplies the missing return semantics — synchronous completion within about a minute, continuation for longer jobs, and where results surface. Prerequisite and quota behavior round out what an agent needs before calling.

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%, so all three parameters are already documented, including the job default and label example. The description reinforces intent ('say so in label') but adds no format or disambiguation details beyond the schema.

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 concrete verb and resource — make an encrypted backup of a server now — and immediately differentiates from the siblings backup_list (long-running archives land there) and backup_job_create (needed when no confirmed job exists).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to call it ('BEFORE a risky change — a migration, a config rewrite, a bulk delete') and routes to the alternative when prerequisites fail ('if it has none, propose one with backup_job_create'), including the caveat that a draft cannot be run.

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.