Skip to main content
Glama

pbs_user_update

Update a PBS user account: enable or disable login, set expiry, names, email, and clear properties. Dry-run shows plan; confirm executes changes.

Instructions

MUTATION (MEDIUM): update a PBS user (enable=False stops login immediately). Dry-run by default — the PLAN reads the user's current config first.

NOTE: this tool does NOT accept a password parameter — PBS's own PUT /access/users 'password' field is documented as ignored ("use PUT /access/password instead"); exposing a working-looking no-op parameter here would mislead a caller into thinking it changed the password.

confirm=True executes and returns a dict; synchronous, no UPID. Use pbs_user_get to see current state first, or pbs_user_delete to remove the user instead. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoOptional email address; omit to leave unchanged.
digestNoOptional SHA256 config digest to prevent concurrent modifications.
enableNoWhether the account can log in; False stops login. Omit to leave unchanged.
expireNoAccount expiry as a Unix timestamp; omit to leave unchanged.
useridYesPBS user id to update, format 'user@realm'.
commentNoOptional free-text comment; omit to leave unchanged.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
lastnameNoOptional last name; omit to leave unchanged.
firstnameNoOptional first name; omit to leave unchanged.
delete_propsNoProperty names to clear: any of 'comment', 'firstname', 'lastname', 'email'.
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?

With no annotations, the description carries full burden. It discloses mutation risk (MEDIUM), immediate effect of enable=False, dry-run behavior, synchronous execution, and the config requirement. However, it omits permissions/error behavior, though output schema covers return format.

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?

The description is well-structured with a clear first sentence, then details on dry-run, password note, confirm, siblings, and config. Every sentence adds value, though slightly wordy. Could be trimmed without losing meaning.

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?

The description covers purpose, safety (dry-run), key behaviors, alternatives, and config. Given 11 params and mutation complexity, it is comprehensive. Output schema covers return values, so no missing critical information. Minor gaps: no explicit error handling mention.

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?

Schema coverage is 100%, so baseline 3. The description adds value by explaining dry-run vs confirm, the missing password parameter's rationale, and the delete_props list. This context aids parameter understanding beyond the 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 the verb ('update') and resource ('a PBS user'), and gives specific behavior ('enable=False stops login immediately'). It explicitly distinguishes from siblings pbs_user_get and pbs_user_delete, making the tool's unique role unambiguous.

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 gives explicit when-to-use guidance: dry-run by default, confirm=True for execution. It advises using pbs_user_get to inspect current state first and directs to pbs_user_delete for removal. It also warns about the absent password parameter, preventing misuse.

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