Skip to main content
Glama

Back up the whole world

backup_world

Copies the whole world folder to the server’s backup folder with saving paused for a consistent snapshot, so you can safely import large maps or make big changes before proceeding.

Instructions

Copies the whole world folder into the server's own backup folder (the server pauses saving while it copies, so the copy is consistent). Do this before big changes, for example before importing a large map or anything too big for an undo snapshot. The tool never deletes backups.

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_world"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

Adds real context beyond the annotations: saving pauses during the copy so the snapshot is consistent, and 'the tool never deletes backups' reinforces destructiveHint=false. It does not disclose whether a new backup overwrites or accumulates alongside prior ones, how much disk space a world copy consumes, or how the backup is subsequently named/found, which matter for an operation that writes files.

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 tight sentences ordered purpose, side effect, usage trigger, and safety guarantee. Every sentence carries information an agent would otherwise have to guess, and the destination is front-loaded.

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?

With zero parameters, no output schema, and annotations already covering the safety profile, the description covers what to call, why, and the main behavioral caveat. The remaining gap is recovery context — how to locate or restore the produced backup (via restore_world/list_files) — which the description leaves unstated.

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 no parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly presents this as a no-argument operation.

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 concrete verb and resource ('Copies the whole world folder into the server's own backup folder') and makes the destination explicit, so the agent knows exactly what artifact is produced. It implicitly distinguishes itself from snapshot-style siblings by putting backups in the frame of things 'too big for an undo snapshot.'

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 clear trigger ('Do this before big changes, for example before importing a large map') and a contrast case ('anything too big for an undo snapshot') that routes the agent toward this over undo. It stops short of explicit exclusions, such as routine small edits where undo suffices or repeated back-ups that may duplicate storage.

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