Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

create_backup

Destructive

Create a tar.gz backup of a directory on a remote Linux server, automatically generating a timestamped archive name when none is provided.

Instructions

Create a tar.gz backup of a directory. Auto-generates timestamped name if not provided.

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": {
      "server": "<server>",
      "source": "<source>",
      "dest_dir": "<dest_dir>"
    },
    "name": "create_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
serverYes
sourceYes
dest_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds useful behavior beyond that, including the output format (tar.gz) and the automatic timestamped naming when no name is supplied. It says nothing about overwriting existing files, disk-space or permission requirements, or failure behavior, which are the remaining gaps for a destructive mutation.

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 short sentences, front-loaded with the core action and with zero filler. The size is appropriate, though the spareness reflects under-specification rather than tight editing.

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

Completeness2/5

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

This is a destructive four-parameter mutation with 0% schema coverage and no output schema. The definition omits what three parameters mean, whether an existing backup is overwritten, and what a successful result looks like. It is not complete enough for an agent to invoke it confidently.

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%, so the description must carry the full burden for four parameters. It clarifies only 'name' by saying a timestamped value is auto-generated when omitted. The three required parameters, server, source, and dest_dir, are left completely unexplained, including whether paths are absolute or relative and what 'server' selects.

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 gives a specific verb and resource: create a tar.gz backup of a directory. That is unambiguous, and it pairs naturally with the sibling list_backups. It does not explicitly name the sibling or state its scope relative to other backup-related operations, which keeps it out of the top band.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus list_backups or any other tool, no prerequisites (e.g. server reachable, source directory must exist), and no exclusions. An agent must infer the entire usage context.

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