Skip to main content
Glama

fort_backup_list

Lists a Bearfort-hosted site's backup generations newest first so you can identify restore points; restore through the Bearfort dashboard.

Instructions

List the fort's backup generations on Bearfort (newest first, as the worker reports them). Restore is not available here: use the Bearfort dashboard. 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_list"
  }
}

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/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses authentication via BEARFORT_API_KEY and newest-first ordering, but it does not describe pagination, result limits, error behavior, or other operational constraints for a list operation.

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?

The description is three short sentences with no wasted wording. Purpose and ordering are front-loaded, followed by the restore limitation and auth requirement.

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 simple one-parameter list tool, the description covers purpose, ordering, restore exclusion, and authentication. It could be more complete by noting pagination or result-size behavior, but no output schema exists and the schema already documents the parameter.

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% and the single site parameter is already described as a site id that must be hosted on Bearfort. The description reinforces the Bearfort requirement but does not add meaningful parameter semantics 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?

The description states a specific verb and resource: listing the fort’s backup generations on Bearfort. It adds ordering detail (newest first, as the worker reports them) and explicitly rules out restore, which distinguishes it from backup creation and restore workflows.

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?

It explicitly says restore is not available here and directs restore intent to the Bearfort dashboard, giving a clear when-not-to-use condition and alternative. It does not explicitly compare against fort_backup_create or spell out other prerequisites beyond the API key, so it stops short of a full 5.

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