Skip to main content
Glama
fredriksknese

mcp-openmediavault

enumerate_users

Lists all system users on OpenMediaVault NAS, including system accounts, to provide comprehensive user management visibility.

Instructions

Enumerate all system users including system accounts (broader than list_users which may only show OMV-managed accounts)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for enumerate_users tool that executes the tool logic. It calls client.rpc('UserMgmt', 'enumerateUsers', {}) to fetch all system users including system accounts, then returns the result as JSON or an error message.
    async () => {
      try {
        const result = await client.rpc("UserMgmt", "enumerateUsers", {});
        return toolResult(JSON.stringify(result, null, 2));
      } catch (error) {
        return toolResult(`Error enumerating users: ${error}`, true);
      }
    },
  • Input schema definition for enumerate_users tool - an empty object {} indicating the tool takes no parameters.
    {},
  • Complete tool registration for enumerate_users using server.tool(), including the tool name, description, input schema, and handler function.
    server.tool(
      "enumerate_users",
      "Enumerate all system users including system accounts (broader than list_users which may only show OMV-managed accounts)",
      {},
      async () => {
        try {
          const result = await client.rpc("UserMgmt", "enumerateUsers", {});
          return toolResult(JSON.stringify(result, null, 2));
        } catch (error) {
          return toolResult(`Error enumerating users: ${error}`, true);
        }
      },
    );
  • Helper function toolResult() that formats the response content for MCP tools, creating a standardized text response with optional error flag.
    function toolResult(text: string, isError = false) {
      return { content: [{ type: "text" as const, text }], isError };
    }
  • src/index.ts:43-43 (registration)
    Main registration point where registerUserTools() is called to register all user-related tools (including enumerate_users) with the MCP server.
    registerUserTools(server, client);
Behavior2/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 mentions the scope (includes system accounts) but lacks details on permissions required, rate limits, output format, or whether it's read-only. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that front-loads the purpose and includes sibling differentiation. Every word earns its place, with no redundancy or unnecessary details, making it highly concise and well-structured.

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?

Given no annotations, no output schema, and 0 parameters, the description covers purpose and usage well. However, it lacks details on behavioral aspects like permissions or output format, which are important for a tool with no structured data. It's adequate but has clear gaps in context.

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 has 0 parameters with 100% schema description coverage, so the schema fully documents the inputs. The description doesn't need to add parameter information, and it appropriately focuses on usage context. Baseline for 0 parameters is 4, as no compensation is needed.

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 clearly states the verb 'enumerate' and resource 'all system users', specifying it includes system accounts. It explicitly distinguishes from sibling 'list_users' by noting the broader scope, making the purpose specific and differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool vs. alternatives by stating it's 'broader than list_users which may only show OMV-managed accounts'. This directly tells the agent to prefer this tool for comprehensive user enumeration, including system accounts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fredriksknese/mcp-openmediavault'

If you have feedback or need assistance with the MCP directory API, please join our Discord server