Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_get_logs

Lists backup logs for selected clients and filters them by severity to help diagnose backup failures, warnings, and errors.

Instructions

List backup logs.

Args: client_ids: Filter to specific clients (empty = all). log_level: 0 = info and up, 1 = warnings and up, 2 = errors only.

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

Input Schema

NameRequiredDescriptionDefault
log_levelNo
client_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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. 'List' implies a read operation, but nothing is said about log retention, ordering, volume or truncation limits, or whether results span all clients by default; only the filtering semantics are covered.

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?

Front-loaded purpose sentence followed by a compact per-argument block, with no filler. The docstring-style 'Args:' section is slightly machine-formatted but still easy to scan.

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 two optional parameters and an output schema that covers return values, the necessary calling information is mostly present. However, a log-listing tool sitting next to urbackup_get_log should clarify the difference and say whether output is bounded or paginated.

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?

Schema coverage is 0% and the schema also lacks the log_level enum, so the description does real work: it defines client_ids filtering with empty meaning all clients, and maps log_level 0/1/2 to info, warning and error thresholds. Only defaults and null-versus-empty handling are left implicit.

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 logs.' An agent immediately knows the operation is a log listing, though it cannot tell from this text how it differs from the near-identical sibling urbackup_get_log.

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 or when-not-to-use guidance, and no mention of the obvious alternative urbackup_get_log. The parameter notes explain filtering options but do not help an agent choose between this tool and its sibling.

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