Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

linux_user_group_manager

Read-onlyIdempotent

Build Linux and FreeBSD user/group administration commands from structured input, parse /etc/passwd and /etc/group files, and audit for security issues like UID 0 imposters, duplicates, and orphan groups.

Instructions

Linux User and Group Manager Command Builder. Build Linux (and FreeBSD) user/group administration command lines from a structured form, parse pasted /etc/passwd and /etc/group text, and audit that parsed state for problems such as UID 0 imposters, duplicate UIDs/GIDs, orphan primary groups, and system accounts with login shells. The generate action emits useradd / usermod / userdel / groupadd / groupmod / groupdel / chage / passwd / chpasswd (or pw on FreeBSD) command text with per-command explanations and safety warnings; use linux_command_builder instead when you need general find/grep/rsync/tar/ssh commands rather than account management. BUILDS command text only - it never executes any command and never touches the local system. Runs locally on the input you provide (read-only, non-destructive, contacts no external service) and is rate-limited (30 requests/minute for anonymous callers). Returns generated commands plus warnings and an explanation, or parsed user/group rows, or audit findings, or curated pr

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoWhich operation to run. generate builds command lines from input; parsePasswd/parseGroup parse pasted file text; audit cross-checks both files; presets returns the curated input presets.generate
inputNoUsed only when action is generate. The account specification to build commands from.
textNoPasted /etc/passwd (action parsePasswd) or /etc/group (action parseGroup) content, one record per colon-separated line.
passwdNo/etc/passwd content for the audit action.
groupNo/etc/group content for the audit action.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request succeeded.
actionNoThe action that was executed.
resultNoAction-specific payload. generate returns commands/warnings/explanation; parsePasswd returns users; parseGroup returns groups; audit returns findings; presets returns presets.
Behavior5/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds that it never executes commands, is read-only, non-destructive, and rate-limited. 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.

Conciseness4/5

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

Well-structured and front-loaded, but slightly verbose and has a cut-off trailing phrase. Could be more concise.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers overall functionality, safety, and return types (though cut off). Given complexity and presence of output schema, description is sufficiently complete.

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?

Schema description coverage is 100%, so baseline is 3. Description provides high-level context but doesn't add meaning beyond schema for individual parameters.

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 tool builds Linux/FreeBSD user/group admin command lines, parses /etc/passwd and /etc/group, and audits for problems. It distinguishes from sibling linux_command_builder by specifying it is for account management only.

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

Usage Guidelines4/5

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

Explicitly tells when to use linux_command_builder instead for general commands. Also mentions rate limits. Lacks explicit when-not-to-use beyond sibling differentiation.

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/Jambozx/onlinecybertools-mcp-server'

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