Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_get_client_settings

Retrieve a client’s effective backup settings—frequencies, windows, paths, exclusions, and quotas—with the server, group, or client origin for each value.

Instructions

Get settings for a client (backup frequencies, windows, paths, exclusions, quotas, ...). Values show the effective value plus the server/group/client origin.

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": {
      "client_id": "<client_id>"
    },
    "name": "urbackup_get_client_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 full burden, and it does disclose one genuinely useful behavioral trait: returned values are the effective value annotated with server/group/client origin, which tells the agent about inheritance resolution. It does not state that the call is non-mutating, what happens with an unknown client_id, or any permission requirements, which is a real gap for an unannotated tool.

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?

Two sentences, front-loaded with the purpose and then the return-value semantics; no filler. The trailing "..." in the parenthetical list is slightly loose but conveys that the enumeration is non-exhaustive.

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 one-parameter read tool with an output schema, the description covers purpose and return semantics adequately, so return-shape explanation is unnecessary. It is incomplete on the one thing an agent must get right — the meaning and provenance of client_id — and says nothing about error behavior.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter is documented only as an integer titled "Client Id". The description adds nothing about the parameter — not whether it is a numeric database ID, where to obtain it, or how it behaves if invalid — so it fails to compensate for the coverage gap.

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 ("Get settings for a client") and enumerates the setting categories returned (frequencies, windows, paths, exclusions, quotas), so the agent knows exactly what domain this covers. The "for a client" scoping implicitly separates it from the general/mail settings siblings, though no sibling is named explicitly.

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: the verb "Get" signals a read operation and the paired save_client_settings sibling is not referenced, nor are prerequisites or exclusions given. An agent can infer this is the read counterpart to saving client settings, but the definition never says so.

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