Skip to main content
Glama
tiancode
by tiancode

pve_vm_set_config

Change configuration of a Proxmox VE VM or LXC container using a dictionary of config values. Hotpluggable changes apply instantly; others are pending until restart.

Instructions

Change configuration options of a VM or container.

    Applies to: QEMU VMs and LXC containers, located by ``vmid`` (``node``
    optional and auto-resolved). ``config`` is a dict of PVE config keys to
    values, e.g. ``{"cores": 4, "memory": 8192, "name": "web02",
    "onboot": 1}`` — the same keys pve_vm_config returns.

    Side effects: updates the guest config. NOTE: most changes (cores,
    memory without hotplug, disks, NICs) only take effect after the guest
    is restarted; PVE applies hotpluggable changes immediately and stages
    the rest as "pending". Waits up to PVE_MCP_TASK_WAIT seconds when PVE
    runs the change as a task; returns JSON with ``vmid``/``node``/``type``/
    ``applied`` (the submitted config) and ``task``.
    Source: POST /nodes/{node}/qemu/{vmid}/config (async) or
    PUT /nodes/{node}/lxc/{vmid}/config (LXC has no async variant).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNo
vmidYes
configYes

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 behavior: it updates guest config, notes that most changes require restart, explains hotplug vs pending, mentions task waiting and source endpoints. This is comprehensive and transparent.

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 well-structured with clear sections, front-loaded purpose, and no unnecessary words. Every sentence adds value, making it efficient and easy to parse.

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 complexity (nested config object, async/sync behavior, side effects), the description covers all key aspects: input parameters, behavior, output schema, task handling, and endpoints. It is complete for an agent to invoke correctly.

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 description coverage is 0%, but the description adds meaning by explaining 'config' is a dict of PVE config keys with examples, and notes 'node' is optional and auto-resolved. 'vmid' lacks additional semantic detail but is straightforward.

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 it changes configuration options of a VM or container, specifies the resource type (QEMU VMs and LXC containers), and distinguishes from siblings like pve_vm_config which is for reading. It uses a specific verb 'change' and identifies the resource 'configuration'.

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?

The description implies when to use (to change config) and explains side effects and the need for restart, which helps decide if this tool is appropriate. However, it does not explicitly compare to alternatives like pve_vm_config or pve_vm_resize_disk, leaving room for ambiguity.

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/tiancode/pve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server