Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_save_client_settings

Update only the settings you want to change for a URBackup client; explicit confirmation is required to apply the modifications.

Instructions

Update settings for a client. Only pass the keys to change. confirm=true required. Examples: {"default_dirs": "C:\Users|User files"} {"update_freq_incr": 14400} {"exclude_files": ".mp3;.avi"}

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>",
      "settings": "<settings>"
    },
    "name": "urbackup_save_client_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
settingsYes
client_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose partial-update semantics and the confirm requirement. It does not cover permissions, whether omitted settings are preserved, reversibility, or side effects, leaving meaningful gaps for a mutation tool.

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 compact and front-loaded: purpose, partial-update rule, confirm requirement, then concrete examples. Every sentence carries usable information and there is no filler.

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?

The output schema means return values need not be explained, but with no annotations, 0% schema coverage, and an open nested settings object, the description leaves gaps around auth requirements, valid settings keys, and update semantics beyond partial key passing. It is adequate for a basic call but not fully complete for safe mutation.

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 compensate; it explains that settings is a partial key/value update and that confirm must be true, with examples for three setting keys. It does not document client_id or the full range and allowed formats for the open settings object, so compensation is only partial.

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 states a specific verb-resource pair, 'Update settings for a client,' and the 'for a client' scope implicitly separates it from general or mail settings siblings. It stops short of explicitly naming alternatives, so it is clear but not maximally differentiated.

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?

It supplies important invocation rules: only changed keys should be passed, and confirm=true is required. However, it gives no explicit guidance on when to choose this tool over get_client_settings or save_general_settings, so usage is implied rather than fully directed.

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