Skip to main content
Glama

pve_role_create

Create a custom role with optional privilege set. Dry-run by default; use confirm=True to execute.

Instructions

MUTATION: create a custom role with an optional privilege set. Dry-run by default (MEDIUM risk — inert until an ACL entry references it). confirm=True executes and returns a dict, synchronous with no UPID. privs format: comma-separated privilege names (e.g. 'VM.PowerMgmt,VM.Config.Disk'). Use pve_acl_modify to assign the new role to a principal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
privsNoComma-separated privilege names for the role, e.g. 'VM.PowerMgmt,VM.Config.Disk'.
roleidYesNew role id.
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
Behavior5/5

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

The description fully discloses that it is a mutation, default dry-run (inert until ACL reference), confirm=True executes synchronously with no UPID, and risk level (MEDIUM). Since no annotations are provided, the description carries the full burden and does so thoroughly.

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 concise, front-loaded with 'MUTATION: create...', and every sentence provides useful information. No redundancy, and it is well-structured.

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 the presence of an output schema (mentioned to return a dict), the description covers all essential aspects: purpose, parameters, behavior, related tool. It is complete for an agent to select and invoke correctly.

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 specifying the privs format (comma-separated list) and example, and reiterates the confirm parameter behavior. This exceeds the schema's own 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 a custom role with an optional privilege set', uses specific verb+resource, and distinguishes from siblings like pve_role_delete, pve_role_update, and pve_roles_list. It also mentions the related pve_acl_modify for assigning roles.

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 specifies when to use (create a custom role) and directs to pve_acl_modify for assignment. It also explains the dry-run vs execute behavior. However, it does not explicitly state when not to use it (e.g., for updating or deleting).

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