Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_memory_vm

Resize VM memory and configure ballooning to control RAM allocation dynamically.

Instructions

Update RAM memory size and ballooning configuration of a VM.

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": {
      "node": "<node>",
      "vmid": "<vmid>",
      "memory": "<memory>"
    },
    "name": "update_memory_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
memoryYes
hugepagesNo
ballooningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It says 'update' but does not reveal side effects like whether a reboot is needed, whether memory values are in MB, or whether changes are immediate. It also completely omits the hugepages parameter, which is part of the schema, leaving significant behavioral aspects undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but under-specified. It omits key parameters and behavior, making it too terse for the tool's complexity. While it is front-loaded and easy to read, it sacrifices necessary information for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters, no annotations, and no output schema, the description is not complete enough for correct invocation. It does not cover all parameters (hugepages missing), does not explain units or side effects, and provides no context about VM state or prerequisites. The tool is a mutation with minimal guidance, which is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It clarifies memory and ballooning, but it does not explain node, vmid, or hugepages. Memory units are not specified, and hugepages is entirely absent, so an agent cannot infer the meaning of all parameters.

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 the tool updates 'RAM memory size and ballooning configuration' of a VM, which is a specific action on a specific resource. This distinguishes it from sibling tools like update_cpu_vm and resize_vm_disk, making the purpose easy to identify.

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?

The description implies the tool is for memory-related updates, but it does not explicitly state when to use it versus alternatives, nor does it mention any prerequisites such as VM state or whether the VM must be stopped. It provides no exclusions or alternative tool names, leaving usage guidance implicit.

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