Skip to main content
Glama

backup_miniserver

Backs up the current Miniserver program as XML and a readable text view into a local Git repository, reports changes since the last backup, and saves nothing when nothing changed.

Instructions

Backs up the program currently running in the Miniserver (newest file in /prog via FTP, download only) as XML plus a readable text view into a local Git repository and reports what changed since the last backup. Nothing is stored if nothing changed.

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": "backup_miniserver"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.9/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 well: it discloses the data path (FTP download only, no upload), what gets written (XML + readable text into a local Git repository), the reporting behavior (what changed since last backup), and the important idempotency trait 'Nothing is stored if nothing changed.' It still omits auth/credential requirements, where the Git repo lives, and how failures (unreachable Miniserver) surface.

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 sentences, zero filler, and the core action plus its side effect are front-loaded before the no-op guarantee. Each clause adds information an agent would otherwise have to guess.

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 zero-parameter side-effecting tool with no annotations and no output schema, the description covers purpose, mechanism, destination, change reporting, and idempotency. The remaining gap is operational context (FTP credentials/configuration, repository location, failure behavior) needed to call it confidently in a fresh environment.

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?

The tool takes zero parameters, which is the baseline 4 case; nothing needs documenting and the description correctly implies the operation is parameter-free by describing implicit sources (newest file in /prog) rather than inputs.

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 names a specific verb ('backs up') and a precisely scoped resource (the program currently running in the Miniserver, sourced from the newest file in /prog via FTP) plus the outputs (XML and text view into a local Git repo). No sibling in the provided list performs backups, so no differentiation is strictly needed, but it also never explicitly excludes other project-state tools like project_changes.

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?

Usage is implied rather than stated: an agent can infer 'call this to snapshot the running program', and 'download only' signals a read-then-write-local flow, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (FTP connectivity, an existing local Git repo), and no alternatives named.

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