mcp-openmediavault

get_user_privileges

Obtain all shared folder privileges assigned to a specified user to review and manage file access on OpenMediaVault.

Instructions

Get all shared folder privileges assigned to a specific user

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>"
    },
    "name": "get_user_privileges"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Username to get privileges for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates a read operation with no side effects, but does not disclose any potential limitations or prerequisites. Basic transparency, no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence with no extraneous information. It is efficiently front-loaded, earning its place.

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?

Given the absence of an output schema and annotations, the description lacks details about the output format, types of privileges returned, or any constraints. It is complete only for a very basic understanding, leaving significant gaps for agent decision-making.

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?

The input schema has 100% description coverage for the single parameter 'name' with a clear description. The tool description adds no additional parameter context, but the schema sufficiently covers it, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all shared folder privileges assigned to a specific user' clearly specifies the verb 'get', the resource 'shared folder privileges', and the target 'specific user'. It distinguishes from siblings like 'get_shared_folder_privileges' which likely target folders rather than users.

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 description implies usage for retrieving privileges per user but provides no explicit guidance on when to use this tool versus alternatives like 'get_shared_folder_privileges' or other user-related tools. Lacks when-not-to-use or context for selection.

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