Skip to main content
Glama

pve_role_update

Update a Proxmox role's privileges with a dry-run preview. Append new privileges or replace existing ones, then confirm to apply changes.

Instructions

MUTATION: change a role's privileges. Dry-run by default — built-in roles (Administrator, PVEAdmin, …) are flagged HIGH (changing them re-scopes every ACL using them). confirm=True executes and returns a dict; synchronous, no UPID. Use pve_roles_list to see current roles and privileges first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
privsNoComma-separated privilege names to set (or add, if append=True).
appendNoIf True, add `privs` to the role's existing privileges instead of replacing them.
roleidYesRole id to update.
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
Behavior4/5

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

No annotations present, so description carries full weight. It discloses mutation behavior, dry-run by default, high impact warning for built-in roles, synchronous execution, no UPID, and dict return type. Missing authorization requirements but sufficient for core behavior.

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?

Three sentences, front-loaded with 'MUTATION' and key behavior. Each sentence adds essential value with no fluff. Efficiently communicates purpose, behavior, and usage guidance.

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?

Given output schema exists, no need to explain return values. Description covers dry-run vs execution, risk of built-in roles, and suggests a preparatory sibling tool. Helps the AI agent understand the full workflow for this mutation.

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 is 3. Description mentions the confirm parameter's effect but adds no new meaning beyond schema. Does not explain privs or append parameters beyond what schema provides.

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?

Description clearly states it is a mutation to change a role's privileges, with specific verb 'change' and resource. It distinguishes from create/delete/list operations in sibling context.

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, need confirm=True to execute, warns about high impact on built-in roles, and recommends using pve_roles_list first. Lacks explicit exclusion for deletion but implied by tool name.

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