Skip to main content
Glama
Sign In

Termalin

by in.termal
OverviewDiscussionsAdmin

backup_job_create

Propose a new encrypted backup job for one of the user's servers: folders and/or databases, how often, how many copies to keep, where to store them. It is saved as a DRAFT in the owner's Termalin cabinet and nothing runs yet; the result has a link the owner opens to confirm it with one click — that creates the job's encryption key, which only the owner holds and which can't be made here. Give them the link and say what the job will back up. Drafts expire after 7 days and count against the plan's job limit. Databases are dumped on the server (Linux or macOS) with pg_dump / mysqldump, also inside a running Docker container, into a .sql file in the archive. No database password is passed or stored: the dump signs in through the local socket (PostgreSQL as the 'postgres' system user by default, MySQL/MariaDB as root's socket login), with a credentials file the owner keeps on the server (a .pgpass or my.cnf path), or — in a container — with the container's own settings (POSTGRES_USER, MYSQL_ROOT_PASSWORD).

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

Input Schema

NameRequiredDescriptionDefault
hostYesServer id or exact name from hosts_list
hourNoHour of day in UTC for daily and weekly runs (default 3)
nameNoJob name shown to the owner, e.g. 'web-1 site and database'
pathsNoAbsolute folders to back up: /var/www, /etc/nginx (on Windows C:\inetpub). May be empty when databases are given.
excludesNoPatterns to leave out: node_modules, *.log, cache
scheduleNoHow often (default daily; weekly runs on Sunday)
databasesNoDatabases to dump into the archive (Linux and macOS servers)
keep_lastNoHow many archives to keep (default 7)
destinationNoWhere to store archives: the name of one of the owner's storages from backup_list (default: Termalin storage)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond the annotations (readOnlyHint=false, destructiveHint=false) by explaining that nothing actually runs yet, that the returned link triggers key creation which 'can't be made here', and that only the owner holds the key. It also discloses side effects an agent could easily get wrong: drafts expire after 7 days, count against the plan limit, and no database password is ever passed or stored.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The essential draft/link behavior is correctly front-loaded, but the body is a single dense paragraph with semicolon-chained clauses and deep pg_dump/socket-auth detail that could be split into scannable structure. It is informative rather than padded, but the packaging works against quick reading.

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, and the description compensates fully by stating what comes back (a confirmation link the owner opens with one click) and what the agent should do with it. For a 9-parameter, non-idempotent mutation tool, nothing needed to call it correctly is 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?

With 100% schema coverage the baseline is 3, but the description adds real semantics: how databases are dumped (pg_dump/mysqldump, including inside a running Docker container into a .sql file) and how authentication resolves via local socket, credentials file, or container environment variables. This makes the credentials_file, container, and user parameters meaningfully clearer than the schema alone.

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?

The description opens with a specific verb+resource: 'Propose a new encrypted backup job for one of the user's servers', and the draft framing ('saved as a DRAFT ... nothing runs yet') functionally separates it from a live-create operation. It never names the sibling 'backup_create', however, so the agent must infer the distinction rather than being told it directly.

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?

Usage context is clear: propose a job, then 'Give them the link and say what the job will back up', plus the constraint that drafts expire in 7 days and count against the plan's job limit. It stops short of explicit when-not guidance or naming which sibling to use instead of this one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Termalin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources