Skip to main content
Glama

pve_user_create

Create a Proxmox VE user account. Runs as a dry-run by default to preview changes; set confirm=True to execute.

Instructions

MUTATION: create a user. Dry-run by default (note: password is set separately — the user cannot log in until then). confirm=True executes and returns a dict; synchronous, no UPID. Use pve_user_update to change it afterward, or pve_user_delete to remove it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoOptional email address.
enableNoWhether the account can log in; None defers to PVE's default (enabled).
expireNoOptional account expiry as a Unix timestamp; None means no expiry.
groupsNoComma-separated list of group ids to add the user to.
useridYesNew user id, format 'user@realm'.
commentNoOptional free-text comment.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
lastnameNoOptional last name.
firstnameNoOptional first name.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes mutation behavior, dry-run vs execution, synchronous nature, and no UPID. However, lacks information on error handling, permissions, or idempotency, but given no annotations, still provides good context.

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?

Three concise sentences that front-load purpose and key behavior. Every sentence adds value with no waste.

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

Completeness5/5

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

Given 10 parameters, rich schema, and output schema existence, the description covers mutation type, dry-run, execution details, password note, and sibling references. Fully sufficient for an AI agent.

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 coverage is 100% with detailed descriptions for all 10 parameters. The description adds only the confirm behavior, which is already in schema. No additional semantic value beyond schema.

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 'MUTATION: create a user' and distinguishes from sibling tools pve_user_update and pve_user_delete, with specific verb and resource.

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?

Explicitly says when to use dry-run (default) vs confirm=True, notes that password is set separately so the user cannot log in until then, and advises using pve_user_update or pve_user_delete for subsequent actions.

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/john-broadway/proximo'

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