Skip to main content
Glama

Get effective permissions

proxmox_get_permissions
Read-only

Show effective Proxmox privileges per path for the current API token/user or another user/token to diagnose 403 permission failures. Filter by a single path such as /vms/100.

Instructions

Show effective privileges per path for the API token/user this server uses (default) or for another user or token. The first thing to check when a tool fails with 403 / 'Permission check failed': it shows exactly which privileges are held where. Use path to check a single path such as /vms/100.

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_get_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOnly this path, e.g. /vms/100 or /storage/local
useridNoUser or full API token ID (user@realm!token) to check (default: the caller)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/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 safety is covered. The description adds meaningful context not in the annotations: which identity is evaluated by default (the server's own token/user) and that the output is per-path privilege mapping. It does not describe output shape or any limits, which keeps it from a 5.

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 short sentences, each load-bearing: purpose first, then the 403 troubleshooting trigger, then a parameter hint. No filler or restated title.

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 two-optional-parameter read tool with no output schema, the description covers what it returns conceptually ('exactly which privileges are held where'), the default identity, and the primary diagnostic use case. It could say more about the shape/scope of the per-path results, but nothing needed to invoke it correctly is missing.

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% and both parameters already document the default caller and path examples. The description's 'Use `path` to check a single path such as /vms/100' mostly restates the schema, so it earns the baseline rather than more.

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?

States a specific verb and resource ('Show effective privileges per path') plus its scope: the caller's own token/user by default, or another user/token on request. That purpose is unmistakably distinct from the surrounding get_* catalog (API tokens, groups, firewall rules), so no sibling name is needed.

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?

Gives an explicit, concrete trigger – 'The first thing to check when a tool fails with 403 / Permission check failed' – which directly routes an agent to this tool. It also tells the agent how to narrow to one path. It stops short of stating when NOT to use it or naming any alternative, so it falls one step below the top band.

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