Skip to main content
Glama

List snapshots across all guests

proxmox_list_all_snapshots
Read-only

Lists snapshots for every VM and container in a Proxmox cluster, oldest first. Filter by node, guest type, or age in days to find stale snapshots holding storage space and slowing disks.

Instructions

List snapshots of every VM and container in the cluster (or a filtered set), oldest first, with guest, node, time, age in days and description. Use older_than_days to find stale snapshots that hold back storage space and slow down disks. Guests whose snapshots can't be read are reported under errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_all_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoOnly guests on this node
typeNoOnly VMs or only containers
limitNoMaximum number of results (default 500)
vmidsNoOnly these guests
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
older_than_daysNoOnly snapshots older than this many days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds ordering (oldest first) and, notably, that unreadable guests are surfaced under an errors key, which is real behavioral disclosure beyond the annotations. It says nothing about pagination or the default 500 result cap, which matters for a cluster-wide listing.

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?

Two tight sentences: the first front-loads scope, ordering, and returned fields; the second delivers the primary use case and the error behavior. No filler and nothing buried.

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 compensates by enumerating returned fields (guest, node, time, age in days, description) and the errors section. It leaves the result-count default and pagination behavior unexplained, which is a moderate gap for a 7-parameter cluster-wide 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 86%, so the baseline is 3. The description adds genuine meaning for older_than_days by tying it to the stale-snapshot use case, and its scope phrasing signals that node/type/vmids narrow the result set, pushing slightly above baseline.

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 with explicit scope: 'List snapshots of every VM and container in the cluster (or a filtered set)'. That scope statement implicitly but clearly distinguishes it from a per-guest snapshot lister, and it names the returned fields, so an agent knows exactly what it gets.

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 scenario: use older_than_days to find stale snapshots that hold back storage space and slow down disks, which tells the agent when this tool is the right diagnostic. It stops short of naming an explicit alternative for single-guest snapshot lookups or stating when not to use it.

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