Skip to main content
Glama

Get guest memory blocks (agent)

proxmox_get_guest_memory_blocks
Read-only

Retrieves a running VM's guest-visible memory blocks, including block size and online block count, so you can verify memory hotplug results.

Instructions

Show a running VM's memory blocks as the guest sees them (QEMU guest agent get-memory-blocks/get-memory-block-info): block size and how many blocks/how much memory is online. Useful after memory hotplug. VMs only; not all guest OSes support it.

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": {
      "vmid": "<vmid>"
    },
    "name": "proxmox_get_guest_memory_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish read-only, closed-world behavior, and the description adds useful preconditions: agent-backed, VM-only, OS-dependent support. It does not say what happens when the guest agent is absent or stopped — the most likely failure mode — nor why idempotentHint is false for a read; a 3 reflects solid but incomplete added context.

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?

One front-loaded sentence describing the output, followed by a short usage sentence and a short limitation clause. No filler or restatement of the title.

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

Completeness4/5

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

With no output schema, the description does describe the shape of the result (block size, number of blocks, memory online), which covers the main gap. What is missing is error/empty-case behavior when the agent is unavailable or unsupported by the guest OS.

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%, and the description says nothing about vmid or the optional node parameter (auto-resolution is already documented in the schema). Baseline 3 is appropriate since the schema carries all parameter meaning.

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?

States a specific verb and resource ('Show a running VM's memory blocks as the guest sees them'), names the underlying QEMU agent calls, and enumerates what is reported (block size, block count, online memory). This clearly separates it from sibling guest-agent reads such as filesystems, network, or users.

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?

Gives a concrete usage situation ('useful after memory hotplug') plus scope limits ('VMs only; not all guest OSes support it'). It does not name an alternative tool for containers or non-agent memory stats, but the exclusions are explicit enough to steer selection.

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