Skip to main content
Glama

Get role

proxmox_get_role
Read-only

Retrieve the privileges of a Proxmox role, grouped by area such as VM, Datastore, and System. Use the role ID to inspect exactly which permissions a role grants.

Instructions

Get the privileges of one role, grouped by area (VM, Datastore, Sys...).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "roleid": "<roleid>"
    },
    "name": "proxmox_get_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleidYesRole ID, e.g. PVEVMAdmin (see proxmox_list_roles)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description contributes a useful behavioral detail beyond them: the returned privileges are grouped by area (VM, Datastore, Sys), which tells the agent how to read the response. It does not cover error behavior for an unknown role or any permission requirements.

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?

A single front-loaded sentence with no filler; the parenthetical area examples support the grouping claim rather than padding. Slightly informal but efficient.

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 one-parameter read-only getter with full schema coverage and no output schema, the description covers purpose and the shape of the return value. The only real omission is guidance on pairing it with proxmox_list_roles to resolve role IDs, which the schema already supplies.

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 description coverage is 100%; roleid is documented there with an example (PVEVMAdmin) and a pointer to proxmox_list_roles. The description adds no further meaning to the parameter, so the baseline 3 applies.

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 names a specific verb and resource ('Get the privileges of one role') and adds scope ('one role') plus the shape of the result ('grouped by area'). It is clearly distinct from list-style siblings such as proxmox_list_roles, though that differentiation is made in the schema rather than the description itself.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named in the description. A reader must infer that this is the per-role lookup companion to proxmox_list_roles from the schema's parameter note instead.

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