Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_usage_stats

Retrieve storage usage per backup client, including file and image bytes used, to monitor disk consumption and identify clients consuming backup space.

Instructions

Storage usage per client (file + image bytes used).

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

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.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 disclosure burden, and it delivers little: it implies a read-only aggregation but never says so explicitly, nor does it mention authentication/permission needs or the scope of aggregation (all clients vs. active). The one useful behavioral detail is the file + image byte breakdown, which tells the agent what the numbers represent.

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 short sentence with the primary noun and the metric definition front-loaded, no filler. It is efficient but borders on under-specification, so it does not quite earn top marks for structure.

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?

An output schema exists, so return-shape explanation is not required, and with no parameters the definition covers the minimum. However, for a tool sitting next to urbackup_usage_graph, the definition leaves the selection decision entirely unresolved, which is the one piece of context an agent actually needs here.

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; the baseline for a parameterless tool applies. The parenthetical clarifying the units being counted is a small bonus over an empty schema.

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 names a specific resource and dimension: storage usage per client, broken into file bytes and image bytes. It is clear what data the tool reports, but it makes no attempt to distinguish itself from the similarly named sibling urbackup_usage_graph, leaving the agent to infer the difference from the names alone.

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 statement of when to use this tool, when not to, or which alternative to prefer. Since sibling urbackup_usage_graph plausibly overlaps in purpose, the absence of any routing guidance is a real gap, not just an omission of boilerplate.

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