Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_save_general_settings

Update URBackup general server settings by sending only changed keys; confirm=true is required. Check current values with get settings first.

Instructions

Update general server settings. Only pass the keys to change. confirm=true required. See urbackup_get_general_settings for current values.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
settingsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose that this is a mutation, that updates are partial/merge-style ('only pass the keys to change'), and that confirm=true is required. It says nothing about permissions needed, whether a confirmation gate exists server-side, whether changes are reversible, or whether a restart is triggered — notable gaps for a write operation with no annotation coverage.

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?

Three short sentences, front-loaded with the action, then the partial-update rule, then the confirmation requirement and the pointer to the getter. Nothing is redundant or padded.

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 needn't be explained, and the read-pair pointer covers discovery of valid keys. But for a nested, free-form mutation tool with zero annotation coverage, the description omits the consequences of confirm, failure behavior for unknown keys, and any permission or restart caveats.

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% and the settings object is free-form (additionalProperties), so the description does real work: it defines partial-merge semantics and implies keys should match what the getter returns. It also flags confirm=true as effectively required even though the schema lists only 'settings' as required — useful, but it leaves the valid key vocabulary and value types to inference.

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: 'Update general server settings', which separates it from save_client_settings and save_mail_settings by scope. It also names urbackup_get_general_settings as the read counterpart, giving the agent a clear pairing, though it never explicitly contrasts itself with the other save_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies a read-before-write workflow by directing the agent to urbackup_get_general_settings for current values, and tells the caller to pass only changed keys. It stops short of stating when not to use the tool or what happens if the settings object is empty or contains unknown keys.

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