Skip to main content
Glama

pve_agent_fs

Freeze guest I/O for consistent backups, thaw after snapshot, or run fstrim to reclaim unused storage space via the QEMU guest agent.

Instructions

MUTATION: fsfreeze-freeze, fsfreeze-thaw, or fstrim inside the guest via the qemu-agent.

Requires PROXIMO_ENABLE_AGENT=1, the VMID in PROXIMO_AGENT_ALLOWLIST, and a running guest agent inside the VM. Dry-run by default (returns a PLAN); confirm=True executes and returns {"status": "ok", "result": }. command: fsfreeze-freeze | fsfreeze-thaw | fstrim — freeze stalls guest I/O until thawed, so always pair them. Irreversible; no undo primitive on this plane.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoProxmox node name hosting the guest; auto-detected if omitted.
vmidYesNumeric VM ID of the guest to operate on via the qemu-agent.
commandYesFilesystem operation: fsfreeze-freeze, fsfreeze-thaw, or fstrim.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the command.
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?

With no annotations provided, the description fully discloses mutation nature, irreversible behavior, dry-run plan, and I/O stalling risk. It also notes the raw qemu-agent response on execution.

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?

The description is concise and front-loaded with key information. It could be slightly more structured (e.g., bullet points), but it effectively conveys critical details without redundancy.

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 the tool's complexity (5 parameters, irreversible mutation), the description covers prerequisites, behavior, return values, and safety advice. With an output schema present, it is complete.

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%, so the schema already describes all parameters. The description adds minor context (node auto-detection, command enumeration) but does not significantly enhance understanding beyond the 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 explicitly states the tool performs fsfreeze-freeze, fsfreeze-thaw, or fstrim via the qemu-agent, clearly differentiating it from sibling tools like pve_agent_exec or pve_agent_file_read/write.

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?

It lists prerequisites (PROXIMO_ENABLE_AGENT=1, VMID allowlist, running agent), explains dry-run default vs confirm=True, and warns about pairing freeze/thaw. Lacks explicit when-not-to-use, but the context is sufficient.

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