Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_create_user

Creates a URBackup server user with specified access rights, requiring explicit confirmation before the account is added.

Instructions

Create a server user. rights format: "domain=right;domain=right" e.g. "all=all" or "status=all;progress=all". 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": {
      "name": "<name>",
      "password": "<password>",
      "rights": "<rights>"
    },
    "name": "urbackup_create_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
rightsYes
confirmNo
passwordYes

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?

With no annotations, the description carries the full burden, and it does disclose one meaningful behavior: confirm=true is mandatory. However, it never explains what confirm actually does (safety gate? dry run?), whether the operation is destructive or reversible, what happens if the user already exists, or what permissions the caller needs.

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 fragments, front-loaded with the action, and the rights syntax is given inline with examples — nothing wasted. The terseness borders on cryptic ("server user" is never defined), but it is efficient and easy to scan.

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 need not be described. For a 4-parameter user-creation mutation with zero schema documentation and zero annotations, however, the description is thin: it omits permission requirements, duplicate-user behavior, and the semantics of the confirm gate.

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 every parameter's meaning must come from the description. It adds real value for rights by giving the format string and two concrete examples, and it flags confirm=true as required, but name, password, and the default/effect of confirm are left completely unexplained.

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, "Create a server user," which clearly separates it from siblings such as urbackup_change_user_rights and urbackup_remove_user. It does not explicitly name an alternative, but the create verb plus the rights-format detail leaves little ambiguity about what the tool does.

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 agent learns it must set confirm=true, which functions as an invocation prerequisite, but there is no statement of when to reach for this tool instead of urbackup_change_user_rights or urbackup_change_user_password. No exclusions or preconditions (e.g., admin rights needed) are given.

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