Skip to main content
Glama
gjenkins20

webmin-mcp-server

create_user

Creates a new system user account. Configure username, password, home directory, shell, and user/group IDs.

Instructions

Create a new system user. This is a dangerous operation and is blocked in safe mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverNoServer alias (e.g., 'pi1', 'web-server'). Uses default server if not specified.
usernameYesUsername (lowercase letters, digits, underscores, hyphens)
passwordYesPassword for the new user
real_nameNoFull name or comment
home_dirNoHome directory (default: /home/username)
shellNoLogin shell (default: /bin/bash)
uidNoUser ID (auto-assigned if not specified)
gidNoGroup ID (auto-assigned if not specified)
Behavior4/5

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

With no annotations, the description discloses the dangerous nature and safe mode restriction, providing useful behavioral context. However, it could detail permissions, side effects, or default behavior.

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?

Single sentence is concise and front-loaded with the key action. A bit more context about safe mode exclusion would be helpful but not necessary.

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 the lack of output schema and annotations, the description provides minimal completeness. It highlights danger but omits return value, prerequisites, and configuration defaults.

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?

Input schema covers all 8 parameters with descriptions (100% coverage). The description adds no extra parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states it creates a new system user, distinguishing it from siblings like create_webmin_user. The verb+resource combination is specific and unambiguous.

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?

Description warns it is dangerous and blocked in safe mode, but does not explicitly explain when to use this tool versus alternatives like modify_user or create_webmin_user.

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/gjenkins20/webmin-mcp-server'

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