Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_get_general_settings

Retrieve general URBackup server settings, including backup folder, limits, cleanup windows, speed limits, and quotas, to review or verify server configuration.

Instructions

Get general server settings (backup folder, limits, cleanup window, speed limits, quotas, ...).

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

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.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden, and 'Get' does signal a non-mutating read. However, it says nothing about whether settings are sensitive, whether any permissions are required, or how the values are returned — the existence of an output schema offsets the latter.

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?

One front-loaded sentence with the resource named first and examples in a parenthetical; nothing is redundant. The trailing ellipsis signals a non-exhaustive list but is slightly imprecise.

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 read tool with an output schema, almost nothing else is required — the schema describes the return shape and the description covers scope. Only the routing to the save/client/mail counterparts is left implicit.

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, which is the baseline-4 case. The parenthetical adds useful meaning about which setting groups the response covers, even though there are no parameters to document.

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 ('Get') and resource ('general server settings'), and the parenthetical enumerates the concrete contents (backup folder, limits, cleanup window, speed limits, quotas), which lets an agent distinguish it from the client- and mail-scoped getters. It does not explicitly name the read/write counterpart, so it stops short of full sibling differentiation.

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 only implied by the verb 'Get' and the word 'general' versus the client/mail settings siblings. There is no explicit statement of when to call this rather than urbackup_get_client_settings or that urbackup_save_general_settings should be used for writes.

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