Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

list_backups

Read-only

Lists .tar.gz backup files in a specified directory on a remote Linux server, including file sizes and dates, to help you identify available backups.

Instructions

List .tar.gz backup files in a directory with sizes and dates.

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>",
      "path": "<path>"
    },
    "name": "list_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds the filtering rule (.tar.gz only) and the returned fields, but says nothing about non-recursive vs recursive traversal, behavior when the directory is missing or empty, or remote invocation via 'server'.

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?

A single front-loaded sentence with no filler; the file-type filter and return fields come early. It is efficient but arguably too terse given the undocumented parameters.

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?

For a two-parameter read-only listing tool with no output schema, the description covers purpose, filter, and return fields, which is near sufficient. The unresolved gap is the undocumented 'server' parameter and error/empty-directory behavior, which an agent would need before calling it correctly.

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 carries the full burden and fails: 'a directory' ambiguously maps to 'path' without stating absolute vs relative form, and the required 'server' parameter (apparently the target host for the listing) is never mentioned at all.

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 (list backup files) and narrows scope to '.tar.gz' files in a directory, plus names the returned fields (sizes and dates). It does not distinguish itself from the obvious counterpart create_backup or explain how it relates to list_servers/disk_usage.

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?

The phrase 'in a directory' implies the context of use (inspecting available backups before restoring or cleaning up), but there is no explicit when-to-use statement, no mention of create_backup as the alternative for producing backups, and no prerequisites.

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