Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_save_mail_settings

Update mail server settings for the backup server; optionally send a test email and require explicit confirmation before saving changes.

Instructions

Update mail server settings. Pass testmailaddr to send a test mail. confirm=true required.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
settingsYes
testmailaddrNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It usefully discloses a mutation gate (confirm=true) and a side effect (sending a test mail), which are genuinely beyond the structured fields. It omits whether settings are merged or replaced, what permissions are needed, and what happens when confirm is false, leaving significant behavioral gaps for a write 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?

Three short, front-loaded fragments with no filler; the primary action comes first and the operational hints follow. The telegraphic style is efficient, though slightly clipped for a tool with a complex nested parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Placeholder.

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 description coverage is 0%, so the description must compensate, and it only partly does: it explains testmailaddr and confirm. The one required parameter, 'settings', is a free-form nested object with additionalProperties=true and is given no explanation whatsoever about expected keys. It also asserts confirm=true is required, which does not match the schema's required list containing only 'settings'.

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 opens with a specific verb and resource: 'Update mail server settings.' That is enough for an agent to distinguish it from the read-only counterpart urbackup_get_mail_settings. It stops short of explicitly naming any sibling, so it does not earn a 5.

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 gives operational cues: pass testmailaddr to send a test mail, and confirm=true is required. It never states when to use this versus urbackup_save_general_settings or the getter, and provides no warning about overwriting existing configuration, so usage is only implied.

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