Skip to main content
Glama

asset_backup_run

Compares an enrolled config folder against its last backup and saves only changed files; long initial runs return running=true, so check backup status later.

Instructions

Compare an enrolled config folder now and back up whatever changed.

Waits up to 20 seconds; a longer first backup answers running=true and goes on (check asset_backup_status later).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "asset_backup_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_idNoFolder id from asset_backup_status; empty means this session's folder

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the 20-second wait ceiling, the running=true signal, that first backups are longer, and the follow-up tool. It does not state whether the backup overwrites prior backups, what permissions are required, or whether repeated runs are idempotent.

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?

Two short sentences, zero padding, and the operational caveat about the async long-running case is placed immediately after the core action. Every clause earns its place.

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?

The tool is simple, the schema is fully documented, and an output schema exists, so return values need not be spelled out. The description still covers the one genuinely surprising behavior (a truncated call that reports running=true). Only the mutation-safety details are absent.

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 description coverage is 100% for the single root_id parameter, so the nested schema already explains the default of this session's folder. The description adds nothing about root_id, so the baseline of 3 applies — no harm, no added value.

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 compound verb and resource: compare an enrolled config folder and back up what changed. The scope ('whatever changed', 'enrolled config folder') is precise enough to separate it from asset_backup_status, which it names explicitly.

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?

The second sentence routes the agent to asset_backup_status when the call returns running=true, which is clear conditional guidance. It lacks an explicit 'use this when you want an immediate backup rather than polling' framing, but the implied trigger is unambiguous.

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