Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_add_extra_client

Adds an extra non-client host, such as a NAS, to the status page for monitoring; set confirm=true to proceed.

Instructions

Add an extra (non-client) host to the status page, e.g. a NAS. 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": {
      "hostname": "<hostname>"
    },
    "name": "urbackup_add_extra_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
hostnameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that this is an additive mutation requiring confirmation, but says nothing about required permissions, what happens on duplicate hostnames, whether entries can be removed, or whether state persists — significant gaps for a write operation.

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 short sentences, front-loaded with the purpose and followed by the required confirmation flag. Minimal waste; only minor cost is that the confirm requirement reads like a schema duplicate rather than explaining why it gates the call.

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?

With an output schema present, return values are covered elsewhere, and both parameters get some mention. For a mutation tool with zero annotation coverage and no schema descriptions, though, the description should address permissions and failure/duplicate behavior to be truly complete.

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 description coverage is 0%, so the description must compensate; it does partially by stating confirm=true is required (notably the schema only shows default=false) and by identifying hostname as the extra host to add. However, no hostname format, validation, or case/duplicate rules are given.

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?

A specific verb plus resource: 'Add an extra (non-client) host to the status page,' clarified with a concrete example ('e.g. a NAS'). It goes beyond the name urbackup_add_extra_client by specifying the host is a non-client entry shown on the status page, which no sibling tool touches.

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 implied through the 'non-client, e.g. a NAS' framing and the stated prerequisite 'confirm=true required,' but there is no explicit when-to-use/when-not guidance or contrast with alternatives (e.g. backup-starting or client-settings tools). Adequate but inferential.

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