Skip to main content
Glama

pbs_realm_openid_update

Update an OpenID realm configuration on Proxmox Backup Server. Dry-run by default returns a plan preview; set confirm=True to apply changes.

Instructions

MUTATION (MEDIUM): update an OpenID realm's config. Dry-run by default — the PLAN reads the realm's current config first. client_key, if supplied, is redacted identically to pbs_realm_openid_create's. confirm=True executes and returns a dict; synchronous, no UPID.

NOTE: there is NO username_claim parameter here — the live PBS schema makes it create-only (set it at pbs_realm_openid_create time); PUT is additionalProperties:false, so accepting it here would only hard-fail the whole update server-side. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
realmYesOpenID realm name to update.
digestNoOptional SHA256 config digest to prevent concurrent modifications.
promptNoOpenID prompt parameter; omit to leave unchanged.
scopesNoOpenID scope list, SPACE-separated; omit to leave unchanged.
commentNoOptional free-text comment; omit to leave unchanged.
confirmNoFalse (default) returns a dry-run PLAN preview; True executes the mutation.
defaultNoDefault-realm-on-login flag; omit to leave unchanged.
audiencesNoOpenID audience list string; omit to leave unchanged.
client_idNoOpenID client id; omit to leave unchanged.
acr_valuesNoOpenID ACR list string; omit to leave unchanged.
autocreateNoAutocreate-on-login flag; omit to leave unchanged.
client_keyNoNew OpenID client secret; redacted from all plans/logs/ledger.
issuer_urlNoOpenID issuer URL; omit to leave unchanged.
delete_propsNoProperty names to clear.
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 provides behavioral details: mutation with medium severity, dry-run by default, client_key redaction, synchronous execution, no UPID, and config requirements. It does not discuss reversibility or permission needs beyond the config hint.

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 concise and well-structured with two clear paragraphs. The first paragraph covers core behavior, and the second adds important caveats. No superfluous content.

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 15 parameters, no annotations, and output schema present, the description provides sufficient context: mutation, dry-run, redaction, config requirement, and a key parameter exclusion. It is adequate for correct tool invocation.

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?

Schema coverage is 100%, so baseline 3. The description reiterates client_key redaction (already in schema) but does not add new semantics for other parameters. The note about username_claim absence is helpful but does not directly describe a parameter.

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 explicitly states it updates an OpenID realm's config, distinguishing it from create by noting the absence of username_claim and the dry-run behavior. The verb 'update' and resource 'OpenID realm config' are clearly specified.

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?

It explains the dry-run default and confirm flag for execution, mentions synchronous operation and no UPID, and notes the prerequisite PROXIMO_PBS_* config. However, it does not explicitly guide when to use this tool over sibling tools like get or delete.

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