Skip to main content
Glama

pbs_realm_ad_create

Set up an Active Directory realm for Proxmox Backup Server authentication. Define server, LDAP options, and sync attributes.

Instructions

MUTATION (MEDIUM): create an AD authentication realm. Dry-run by default.

PASSWORD REDACTION: password (the AD bind password), when supplied, is UNCONDITIONALLY redacted from the plan, detail, and audit ledger (only {"password": "[redacted]"} is recorded). confirm=True executes and returns a dict; synchronous, no UPID. Use pbs_realm_ad_update to change it afterward, or pbs_realm_ad_delete to remove it. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoLDAP connection type: 'ldap', 'ldap+starttls', or 'ldaps'.
portNoAD server port.
realmYesNew AD 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 AD server's TLS certificate.
base_dnNoLDAP base DN to search under; optional for 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 AD server address.
server2NoFallback AD server address.
passwordNoAD bind password for the service account; redacted from all plans/logs/ledger.
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
Behavior5/5

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

With no annotations, the description fully carries the burden. It discloses mutation nature, dry-run behavior, password redaction, synchronous execution (no UPID), and configuration prerequisite.

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?

Front-loaded with key information. The second paragraph focuses on password redaction, which is important. No wasted words; slightly verbose but justified given the complexity.

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 18 parameters and high schema coverage, the description covers essential behavioral aspects (dry run, password handling, sync behavior). Output schema exists, so return values are not needed. Could mention more about sync defaults, but overall complete.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the 'confirm' parameter's role (dry-run vs execute) and the 'password' parameter's redaction behavior, which go 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 AD authentication realm' as the primary purpose. It distinguishes from siblings by explicitly referencing pbs_realm_ad_update and pbs_realm_ad_delete for modification and removal.

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 context: dry-run by default, confirm=True to execute, and refers to update/delete tools for subsequent operations. Lacks explicit 'when not to use' but the alternatives are well-specified.

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