Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_change_user_rights

Change a URBackup user's permissions by specifying the user ID and new rights; set confirm=true to apply the change.

Instructions

Change a user's rights. 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": {
      "user_id": "<user_id>",
      "rights": "<rights>"
    },
    "name": "urbackup_change_user_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
rightsYes
confirmNo
user_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add one genuinely behavioral fact beyond the schema — that confirm must be true for this call even though the schema marks it optional with default false — but says nothing about whether existing rights are replaced wholesale, what permissions the caller needs, or whether the change is reversible.

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 with the verb first and the prerequisite second; nothing is wasted. The terseness is efficient rather than padded, though it edges toward under-specification.

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

Completeness2/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, but for a no-annotation mutation tool with zero schema coverage on 'rights', the description leaves an agent unable to construct a correct call. The confirm requirement is the only gap it closes.

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% across three parameters, and the description only addresses 'confirm'. The critical 'rights' string is left completely unexplained (valid values, format, or whether it overwrites), and 'user_id' is never characterized beyond its name.

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 plus resource ('Change a user's rights'), which distinguishes it from siblings like urbackup_change_user_password, urbackup_create_user, and urbackup_remove_user by resource alone. It stops short of naming any alternative explicitly, so it is clear but not fully differentiated in prose.

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?

The only guidance is the prerequisite 'confirm=true required', which tells the agent a guard flag must be set but not when to prefer this tool over the password/create/remove siblings. Usage is implied by the mutation verb rather than stated.

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