Skip to main content
Glama

List directory mounts

proxmox_list_directory_mounts
Read-only

List the directory storages Proxmox manages on a node's disks, showing filesystems mounted under /mnt/pve via systemd mount units.

Instructions

List the directory storages Proxmox manages on a node's disks (filesystems mounted under /mnt/pve/ via systemd mount units).

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.1/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 the safety profile is covered. The description adds implementation context (systemd mount units under /mnt/pve/<name>) that helps the agent interpret results, but says nothing about return shape, ordering, or whether unmounted/disabled storages appear.

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?

A single front-loaded sentence with no filler; the identifying detail (path and mount mechanism) comes immediately after the verb and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list operation with annotations covering safety, the description is adequate on the 'what' side. However, with no output schema and two undocumented parameters (fields, search), the agent lacks enough information to use the schema fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: 'node' is documented in the schema, but 'fields' and 'search' have no description in either the schema or the tool description. The description does not compensate for these gaps — it never mentions filtering by field selection or search, which an agent would need to use those parameters correctly.

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 resource — directory storages Proxmox manages on a node's disks, mounted under /mnt/pve/<name> via systemd mount units — which is far more precise than the title. It distinguishes the concept from raw disks or LVM storage by naming the mount mechanism, though it doesn't explicitly contrast with siblings like proxmox_list_disks or proxmox_list_lvm.

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 when-to-use or when-not-to-use guidance. The agent must infer from the phrase 'directory storages' whether this is the right tool versus the disk, LVM, or backup listing siblings, and no alternative is named.

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