Skip to main content
Glama

fort_backup_create

Start a full Bearfort backup of a site's files and database before risky changes; returns a job ID and status to track progress with fort_job_get.

Instructions

Start a backup of the site's whole fort (files + database) on Bearfort now, e.g. before risky changes. Returns { jobId, status }; follow it with fort_job_get. Audit-logged by Bearfort. Needs BEARFORT_API_KEY.

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": {
      "site": "<site>"
    },
    "name": "fort_backup_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites); must be hosted on Bearfort

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the operation is asynchronous (returns jobId/status) and must be polled via fort_job_get, that Bearfort audit-logs the call, and that BEARFORT_API_KEY authentication is required. It omits idempotency, duration, and concurrency behavior, which keeps it short of a 5.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and scope, then the return shape and next step, then auth. Every clause contributes new information; there is no filler.

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?

For a one-parameter action tool with no output schema, the description supplies the essentials an agent needs: what is backed up, that the result is a job to be polled, and the auth prerequisite. Nothing required for correct invocation is missing.

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?

The single parameter has 100% schema description coverage ('Site id (see list_sites); must be hosted on Bearfort'), so the schema already does the explaining. The description only implies the site via 'the site's whole fort' and adds no format, example, or discovery detail beyond the schema — baseline 3 is appropriate.

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: 'Start a backup of the site's whole fort (files + database)', and clarifies scope as the full fort rather than a partial/list operation. It also names the follow-up tool (fort_job_get), so an agent can immediately distinguish this from the sibling that tracks job status.

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 a concrete trigger ('before risky changes') and the correct next call (fort_job_get). It does not explicitly state when NOT to use it (e.g. to view existing backups, use fort_backup_list), but the usage context is clear enough to select it confidently.

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

Deploy Server

Other Tools