Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_get_log

Retrieve detailed entries for a specific backup log by log_id so you can inspect events and troubleshoot issues.

Instructions

Get the detailed entries of a log (from urbackup_get_logs).

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": {
      "log_id": "<log_id>"
    },
    "name": "urbackup_get_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'Get' and 'detailed entries,' which implies a read operation, but it does not disclose permissions, side effects, limits on returned entries, or other behavioral traits.

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 description is a single front-loaded sentence with no unnecessary wording. Every part contributes to identifying the operation and its source reference.

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 simple one-parameter tool with an output schema, the description gives the essential relation to urbackup_get_logs. However, with no annotations and no schema parameter description, it remains thin on behavioral and parameter context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must clarify log_id. It does imply that log_id identifies a log returned by urbackup_get_logs, which adds useful meaning, but it does not describe the parameter's format, constraints, or required nature beyond what the schema already states.

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, 'Get,' and resource, 'detailed entries of a log,' and relates it to urbackup_get_logs. This distinguishes it from the sibling that lists logs, though it could more explicitly frame the contrast.

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 parenthetical '(from urbackup_get_logs)' implies that the log_id should come from that sibling, giving useful implied usage guidance. However, it does not explicitly state when to use this tool, prerequisites, or when not to use it.

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