Skip to main content
Glama

backup_create

DestructiveIdempotent

Queues a verified database and files backup outside the state directory, releasing task leases before starting.

Instructions

Queue a verified database/files backup outside the state directory. Release task leases before starting.

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": {
      "destination": "<destination>",
      "op_id": "<op_id>"
    },
    "name": "backup_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
destinationYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Goes beyond the annotations by revealing that the operation is asynchronous ('Queue'), that the backup is verified, that the destination must lie outside the state directory, and that task leases must be released first. With destructiveHint=true already declared, it still does not say what is overwritten or destroyed at the destination, which is the one meaningful gap.

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 front-loaded sentences with no filler; the scope constraint precedes the operational caveat. Terseness is close to excessive, but nothing stated is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the mutation/destructiveness is at least flagged by annotations. However, with a required op_id never explained and no destination semantics, an agent cannot confidently construct the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters (op_id, destination) are undocumented in the schema, so the description must compensate — but it never mentions op_id at all and gives no format, path, or overwrite semantics for destination. Both required parameters remain semantically opaque.

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 verb and resource ('Queue a verified database/files backup') plus a scope constraint ('outside the state directory'). It is distinguishable from the surrounding task/batch/check tools, though no sibling is named to route against.

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

Usage Guidelines3/5

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

Adds a real precondition — 'Release task leases before starting' — which tells the agent something must happen first. It never states when to choose this over other operational tools, or what the conditions are for a successful queue, so usage remains implied.

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