Skip to main content
Glama

List roles

proxmox_list_roles
Read-only

List Proxmox VE roles with their privileges to audit permissions and identify built-in versus custom roles. Filter by name or built-in status and optionally return role names only.

Instructions

List roles with their privileges. Built-in roles (Administrator, PVEAdmin, PVEVMAdmin, PVEAuditor, NoAccess...) are flagged builtin=true and cannot be changed. Use privileges=false for names only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
builtinNoOnly built-in (true) or only custom (false) roles
privilegesNoInclude each role's privilege list (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds real behavioral context: built-in roles are flagged builtin=true and cannot be modified, which tells the agent these entries are immutable and would need custom roles for any change. It omits any note on result size or ordering, but the added immutability fact is genuine value.

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?

Three short sentences, front-loaded with the purpose and followed by the built-in caveat and the one actionable flag. The parenthetical list of built-in role names is slightly verbose but concretely useful; no sentence is wasted.

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 zero-required-parameter, read-only list tool with no output schema, the definition covers what is returned (roles with privileges, a builtin flag) and the meaning of the immutability flag. The only gap is the undocumented 'fields' parameter, which an agent could need to control the projection.

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 75%, so the schema already documents search, builtin and privileges. The description's 'privileges=false for names only' restates the schema's 'Include each role's privilege list (default true)' rather than adding new meaning, and the undocumented 'fields' projection parameter is never explained. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource, 'List roles with their privileges', which immediately separates it from siblings such as proxmox_list_acl or proxmox_list_groups. It does not explicitly name a contrasting sibling, but the resource scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage hint is 'Use privileges=false for names only', which is parameter-level advice rather than when/when-not guidance. There is no statement about when an agent should reach for this instead of proxmox_list_acl or other role/ACL-related list tools, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools