Skip to main content
Glama

pve_agent_file_write

Write a file to a Proxmox VM guest via the QEMU agent. Dry-run returns a plan; confirm executes the write, overwriting the target irreversibly.

Instructions

MUTATION: write a file 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": None}. File path must be absolute; content is UNCONDITIONALLY redacted from the ledger (fingerprint only). Overwrites the target file whole — irreversible, no undo primitive on this plane. To read a file instead use pve_agent_file_read; text content round-trips byte-identical, binary/encoded content is unconfirmed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesAbsolute path of the file to write inside the guest.
nodeNoProxmox node name hosting the guest; auto-detected if omitted.
vmidYesNumeric VM ID of the guest to write to via the qemu-agent.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the write.
contentYesFile content to write; unconditionally redacted from the ledger (fingerprint only).
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, the description fully discloses the mutation behavior, dry-run/execution model, content redaction (fingerprint only), overwrite effect, and round-trip caveat for binary content. This is comprehensive.

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?

The description is a single paragraph with front-loaded information. Every sentence adds value without redundancy. It is concise yet covers all essential aspects.

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 output schema exists, the description is complete: it covers prerequisites, usage, behavior, side effects, and return format. No gaps remain for an agent to misuse the tool.

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 context beyond the schema (e.g., redaction behavior, absolute path requirement, dry-run plan). It enhances understanding of the confirm parameter and content handling.

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 begins with 'MUTATION: write a file inside the guest via the qemu-agent,' clearly stating the action and resource. It distinguishes from sibling tools like pve_agent_file_read, which is explicitly mentioned as an alternative.

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?

The description provides explicit prerequisites (PROXIMO_ENABLE_AGENT, allowlist, running agent), explains the dry-run default and confirm flag, warns about irreversibility, and suggests the read alternative for reading.

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