Skip to main content
Glama

Get guest filesystems (agent)

proxmox_get_guest_filesystems
Read-only

Lists a running VM's mounted filesystems via the QEMU guest agent, including mountpoint, type, used/total space and backing disks, to check real disk usage inside the VM.

Instructions

List a running VM's mounted filesystems from inside the guest (QEMU guest agent get-fsinfo): mountpoint, type, used/total space and backing disks. Use it to check real disk usage inside a VM (Proxmox's own disk figures for VMs are not filesystem usage). VMs only.

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": {
      "vmid": "<vmid>"
    },
    "name": "proxmox_get_guest_filesystems"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100

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 cover the read-only and closed-world profile, so the description's job is to add operational context, which it does: the guest must be a running VM and requires the QEMU guest agent, and the data comes from inside the guest rather than the hypervisor. It also warns that results will not match Proxmox's host-side disk figures, which prevents a common misreading. It does not mention behavior when the agent is absent or not running.

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 tight sentences, front-loaded with the action and data source, followed by the motivating use case and the scope restriction. No filler or repetition; every clause carries information an agent needs.

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?

With no output schema, the description compensates by enumerating returned fields (mountpoint, type, used/total space, backing disks), and it states the key prerequisites (running VM, guest agent). The main residual gap is error/empty behavior when the guest agent is missing or stopped, though the behavioral hints largely imply that failure mode.

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% for all three parameters (vmid, node auto-lookup, raw), so the schema already documents their meaning. The description adds domain framing ("running VM", "VMs only") that reinforces what vmid should target, but gives no detail on the raw or node parameters. Baseline 3 applies when the schema does the heavy lifting.

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?

"List a running VM's mounted filesystems from inside the guest" gives a specific verb, resource, and scope, and the parenthetical "(QEMU guest agent get-fsinfo)" names the exact upstream API call. The closing sentences distinguish it from Proxmox's own VM disk reporting, so an agent can tell it apart from sibling disk/stats tools without opening a schema.

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?

"Use it to check real disk usage inside a VM" states the intended use case, and "Proxmox's own disk figures for VMs are not filesystem usage" explains why this tool is chosen over that data source. "VMs only" functions as an exclusion (containers fall to other tools), though no specific sibling 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