Skip to main content
Glama

pbs_user_delete

Remove a PBS user with a dry-run plan previewing tokens and ACLs to be deleted. Confirm to execute permanently.

Instructions

MUTATION (MEDIUM): delete a PBS user. Dry-run by default — the PLAN reads the user's current config and tokens to show what vanishes with it (permanent, no undo — any tokens owned by this user are removed with it, and ACL entries granted directly to this userid become orphaned). confirm=True executes and returns a dict; synchronous, no UPID. To disable login without deleting, use pbs_user_update (enable=False) instead. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digestNoOptional SHA256 config digest to prevent concurrent modifications.
useridYesPBS user id to delete, format 'user@realm'.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
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
Behavior5/5

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

Disclosures mutation type, dry-run default, permanent action (no undo), token removal, ACL orphanage, synchronous behavior, no UPID, and config requirement. Fully transparent given no annotations.

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?

Single paragraph with clear structure: operation, behavior, effects, confirmation, alternative, prerequisite. No wasted words, front-loaded with key info.

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?

Covers operation, plan/execute workflow, side effects, alternative, and prerequisite. With output schema present, no need to explain return values. Complete for a mutation tool.

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?

Description does not add semantic detail beyond the schema's 100% coverage. Mentions confirm but not new parameter info. Baseline 3 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?

Clearly states "delete a PBS user" with specific verb and resource. Distinguishes from sibling pbs_user_update by noting the alternative for disabling login.

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 describes when to use (delete), when not to (disable login via pbs_user_update), and prerequisite config needed (PROXIMO_PBS_*). Also explains dry-run vs execute behavior.

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