Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

edit_guest

Change a Proxmox guest's CPU cores, memory, swap, name, boot order, tags, notes, or other settings, updating only the fields you specify.

Instructions

Change a guest's settings: cores, memory_mib, swap_mib, name, start_at_boot, boot_order, boot_delay_s, shutdown_timeout_s, tags, notes, tablet, cpu_type. Only what is given changes.

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": {
      "host": "<host>",
      "vmid": "<vmid>",
      "changes": "<changes>",
      "reason": "<reason>"
    },
    "name": "edit_guest"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
vmidYesThe guest's ID (VMID).
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
changesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-readOnly, non-destructive and non-idempotent, so the safety bar is lower; the description adds the partial-update contract. It does not explain why the call is non-idempotent, whether changes apply live or require a restart (only cpu_type and tablet say so, and only inside the schema), or what the approval flow does beyond the reason field.

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?

Two sentences, mutation scope front-loaded, with the partial-update rule placed last as a qualifier. The field roster partially duplicates the schema, but it serves as a quick scan of what is editable, so no sentence is wasted.

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 mutation tool with a nested four-parameter schema and no output schema, the description covers what changes but not the outcome: no mention of what is returned, what happens on invalid values, or that some edits only take effect at next start. The rich schema compensates for much of this, leaving moderate gaps.

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 75% and every nested change field carries its own Proxmox-specific documentation, so the baseline of 3 applies. The description only restates the field names already enumerated in the schema, adding no format or constraint information beyond it.

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 opens with a specific verb and resource ('Change a guest's settings') and enumerates the exact mutable fields, so an agent knows precisely what the tool mutates. It stops short of naming the sibling it is not (e.g. guest_power for power state, grow_disk for disks), so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Only what is given changes' implies partial-update semantics, which is the main usage cue and is genuinely helpful. However, there is no explicit guidance on when to reach for this versus guest_power, grow_disk or clone_vm, and no stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.