Skip to main content
Glama

pbs_realm_sync

Sync users from a PBS LDAP/AD realm into PBS. Run a dry-run preview by default; set confirm=true to apply changes and optionally remove users no longer in the directory.

Instructions

MUTATION: sync PBS auth realm (LDAP/AD) users into PBS. Dry-run by default; confirm=True to execute. Async — returns a UPID; check progress with pbs_tasks_list. remove_vanished=True additionally DELETES PBS users no longer present in the directory (recoverable only by re-sync, not a true undo). Needs PROXIMO_PBS_* config. (2026-07-10 audit: the old 'scope' param was dropped — PBS /sync has no such field.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
realmYesPBS LDAP/AD auth realm ID to sync users from.
confirmNoGate: false returns a dry-run PLAN, true executes the sync.
dry_runNoIf true, ask PBS itself to preview the sync without applying it (separate from the tool's own confirm gate).
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.
remove_vanishedNoIf true, also delete PBS users no longer present in the directory.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses async behavior, dry-run versus execution, deletion risk with remove_vanished, and configuration prerequisite. Lacks mention of rate limits or auth specifics, but covers key traits.

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?

One well-structured paragraph that front-loads the core action, then details behavior and warnings. No wasted words.

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?

Given 5 parameters and an output schema, the description covers essential behavioral aspects, async handling, and configuration notes. Could mention expected return format briefly, but overall sufficient.

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%, baseline 3. The description adds value by explaining the confirm gate, the separate dry_run parameter, and the recoverability limitation of remove_vanished. Also notes the deprecated scope param was dropped.

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 it is a mutation that syncs PBS auth realm users, with explicit dry-run default and confirm gate. Distinct from siblings as no other tool does realm sync.

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?

Provides clear usage context: dry-run by default, confirm to execute, async returning UPID, and mentions checking progress with pbs_tasks_list. Does not explicitly list when not to use, but the guidance is sufficient.

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