Skip to main content
Glama

pdm_acl_list

List PDM's access control entries to view authorized users. Optionally filter by path; exact flag restricts to given path only.

Instructions

READ-ONLY: list PDM's own access control entries (who can use PDM, not a managed remote's ACL).

No state change. Returns a list of ACL entry dicts. exact=True restricts to the given path instead of including sub-paths. For a managed PVE cluster's ACL instead of PDM's own, use pve_acl_list. Needs PROXIMO_PDM_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOptional ACL path filter, e.g. '/'; omit to list all entries.
exactNoIf true, match the given path exactly rather than including sub-paths.
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?

No annotations provided, so description carries full burden. It discloses read-only nature, returns list of ACL entry dicts, and explains exact parameter behavior. Transparent about no state change.

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?

Very concise, front-loaded with read-only and purpose. Every sentence adds value. No unnecessary words.

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 it's a list tool with 3 parameters and an output schema, the description covers purpose, usage, behavior, parameters, return type, sibling differentiation, and prerequisites. Complete.

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%, but the description adds value by explaining exact=True restricts to given path and providing example for path parameter. Proxmo_target is well-documented in schema.

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 the tool lists PDM's own ACL entries, not a managed remote's ACL, and is READ-ONLY. It distinguishes the tool's purpose from sibling tools like pve_acl_list.

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

Usage Guidelines5/5

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

Specifies no state change and provides explicit alternative for PVE cluster ACLs (pve_acl_list). Also notes config requirement (PROXIMO_PDM_*).

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