Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_usage_graph

Graph backup storage usage over time by day, month, or year, with optional client filtering to track capacity trends.

Instructions

Storage usage over time.

Args: scale: d = daily, m = monthly, y = yearly. client_id: Optional client to filter by.

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

Input Schema

NameRequiredDescriptionDefault
scaleNod
client_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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, yet it only says what data is covered. It never states that this is a read-only operation, whether it requires authentication or an active server, or how large a time range is practical for the daily scale.

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 front-loaded sentence followed by terse per-argument notes; nothing is wasted. The docstring-style 'Args:' block is slightly mechanical but stays compact and readable.

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 values need not be described, and both arguments are covered in the text. What's missing is how this tool relates to urbackup_usage_stats and any hint about the behavior of the daily/monthly/yearly aggregation.

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% for the two parameters, but the description compensates well: it decodes the scale codes (d = daily, m = monthly, y = yearly) that the schema leaves as an unconstrained string, and clarifies that client_id is an optional filter. Only the default value 'd' is left undocumented in the text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Storage usage over time" names the resource (storage usage) and the temporal dimension, so the agent knows it's a time-series reporting tool. But it never says what is returned (a graph/plot vs. raw numbers) and does not distinguish it from the sibling urbackup_usage_stats, leaving ambiguity about which usage tool to pick.

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 closely named urbackup_usage_stats alternative. The only implicit signal is the 'over time' phrasing, which an agent must interpret on its own.

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