Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_list_users

Lists server users and their assigned rights to help you review access permissions and manage accounts.

Instructions

List server users with their rights.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "urbackup_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden. It discloses that rights are included in the response and the read-only nature is implied by "List", but it says nothing about required privileges, result ordering, or whether disabled/service users are included. For a zero-parameter read this is a moderate rather than serious gap.

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?

A single front-loaded sentence with no filler. It is arguably terse to the point of omitting access prerequisites, but nothing in it is wasted or redundant.

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?

Zero parameters, an output schema, and a simple read operation mean little needs saying, and the description covers purpose and payload. It still leaves the access/permission context and the shape of "rights" unexplained, which is a clear but minor gap for this complexity level.

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?

The tool takes no parameters, so there is no parameter meaning to add; the baseline of 4 applies. The phrase "with their rights" usefully signals the payload content even without parameters.

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?

"List server users with their rights" names a specific verb (List), resource (server users), and scope (includes rights). That verb choice naturally separates it from write-oriented siblings like urbackup_create_user, urbackup_remove_user, and urbackup_change_user_rights, though no sibling is named explicitly.

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: an agent can infer this is the read path for user accounts when a mutating sibling such as change_user_rights or create_user is inappropriate. There is no explicit when-to-use statement, no prerequisite (e.g. admin-only) mentioned, and no named alternative.

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