Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_status

Lists all UrBackup clients with online state, last backup times, OS, version, and running processes, plus server-level flags for disk space, database errors, and backup availability.

Instructions

List all UrBackup clients with online state, last backup times, OS, version, and running processes. Also returns server-level flags (disk space problems, database errors, image/file backup availability).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of what comes back, including server-level flags (disk space problems, database errors, backup availability), which signals this is a broad read that surfaces problems rather than just a roster. It says nothing about whether the call is a live server probe (and thus potentially slow or failing), whether authentication is required, or how large client lists are handled.

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, both load-bearing. The primary output (client list with fields) is front-loaded, and the secondary server-level flags are correctly relegated to a follow-on sentence. No filler or redundancy.

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?

With zero parameters and an output schema present, most of the informational burden is already covered structurally, and the description explains the semantic content of the response well. The remaining gap is selection context: with a sibling named urbackup_status_check in the catalog, an agent has no basis from this description for choosing between them.

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, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter hints are present.

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 uses a specific verb ("List") with a specific resource ("all UrBackup clients") and enumerates the per-client fields returned (online state, last backup times, OS, version, running processes), plus server-level flags. That is far more than a restatement of the name. It does not, however, distinguish itself from the near-identically named sibling urbackup_status_check.

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 when-to-use guidance, no prerequisites, and no mention of alternatives, even though urbackup_status_check and urbackup_progress sit in the same catalog and would plausibly be confused with this tool. The agent must infer usage purely from the field list.

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