Skip to main content
Glama

pbs_realm_ldap_create

Create an LDAP authentication realm for Proxmox Backup Server. Requires base DN and user attribute. Dry-run by default; set confirm=True to execute.

Instructions

MUTATION (MEDIUM): create an LDAP authentication realm. Dry-run by default. base_dn and user_attr are REQUIRED (unlike AD, which needs neither on create).

PASSWORD REDACTION: password is UNCONDITIONALLY redacted identically to pbs_realm_ad_create's. confirm=True executes and returns a dict; synchronous, no UPID. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoLDAP connection type: 'ldap', 'ldap+starttls', or 'ldaps'.
portNoLDAP server port.
realmYesNew LDAP realm name.
capathNoPath to a CA certificate file or directory to trust for TLS.
filterNoCustom LDAP search filter for user sync.
verifyNoWhether to verify the LDAP server's TLS certificate.
base_dnYesLDAP base DN to search under (required for LDAP, unlike AD).
bind_dnNoLDAP bind DN for the service account.
commentNoOptional free-text comment.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
defaultNoTrue to make this the default realm preselected on login.
server1YesPrimary LDAP server address.
server2NoFallback LDAP server address.
passwordNoLDAP bind password for the service account; redacted from all plans/logs/ledger.
user_attrYesUsername attribute used to map a userid to an LDAP dn (required for LDAP).
user_classesNoComma-separated allowed objectClass values for user sync.
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.
sync_attributesNoComma-separated key=value LDAP-attribute-to-PBS-field sync map, forwarded verbatim.
sync_defaults_optionsNoDefault sync-run options string, forwarded verbatim (exact syntax not live-verified).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/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 type, dry-run default, confirm behavior, synchronous execution (no UPID), and password redaction. Missing details include authorization requirements, idempotency, and potential conflicts if the realm already exists.

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?

The description is three lines, front-loaded with 'MUTATION (MEDIUM): create an LDAP authentication realm.' It efficiently packs key details (dry-run, required fields, password redaction, config) with no extraneous 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?

For a tool with 19 parameters and an output schema, the description covers purpose, dry-run, confirm, password redaction, and config requirement. It doesn't detail error handling or prerequisites but provides sufficient context for typical use. Output schema covers return values.

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 is 3. The description adds value by highlighting that base_dn and user_attr are required for LDAP (unlike AD) and explaining the confirm parameter's role. This extra context enhances understanding beyond schema descriptions.

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 'create an LDAP authentication realm', specifying the action (create) and the resource (LDAP realm). It distinguishes from the AD counterpart by noting required parameters (base_dn, user_attr) that differ, making the tool's purpose unambiguous.

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?

The description notes that the tool is dry-run by default, with confirm=True to execute. It mentions the need for PROXIMO_PBS_* config and contrasts required fields with AD. However, it does not explicitly state when to use this tool vs alternatives (e.g., pbs_realm_ad_create) beyond the LDAP vs AD difference.

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