Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_status_check

Runs the server health check for all clients, covering connectivity, settings, and backup state, and returns the results.

Instructions

Run the server's health check for all clients (connectivity, settings, backup state) and return the results.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It identifies the diagnostic scope and that results are returned, but does not explicitly state that the check is read-only, whether it has side effects, or what permissions are required. 'Health check' implies a safe diagnostic operation, but that is left implicit.

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?

The single sentence is front-loaded, appropriately sized, and every clause contributes useful scope information about what is checked and returned. There is no filler.

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 tool with an output schema, the description supplies enough context about the check scope and result return. The main remaining gap is distinguishing this tool from the sibling 'urbackup_status', but the essential information for invoking it correctly is present.

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 no parameter semantics burden for the description to address. The baseline for zero parameters is 4.

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 ('Run the server's health check') and clarifies scope ('for all clients') and checked dimensions ('connectivity, settings, backup state'). It does not explicitly differentiate this from the sibling 'urbackup_status', so it falls short of a 5.

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 by the health-check purpose, but the description gives no explicit when-to-use guidance, prerequisites, or alternatives to compare against 'urbackup_status' or other sibling tools. Minimum viable guidance only.

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