Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

list_snapshots

Read-onlyIdempotent

Retrieve a guest's snapshots on a Proxmox host using its host ID and VMID, so you can review available restore points before rollback or cleanup.

Instructions

A guest's snapshots.

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>"
    },
    "name": "list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
vmidYesThe guest's ID (VMID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no indication of whether results are paginated, what happens with a missing VMID, or whether snapshot metadata or sizes are included.

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

Conciseness2/5

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

It is only four words and contains no wasted words, but it is under-specified rather than concise — the single fragment earns little of its place. There is no front-loaded statement of what the tool actually returns.

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?

This is a simple read-only list tool with full schema coverage and no output schema, so expectations are modest, but the description still omits the basic contract: what is returned per snapshot and any ordering or scoping behavior. An agent could invoke it, but only by guessing from the name.

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 description coverage is 100%, with host ("from list_hosts") and vmid already documented in the schema, so the baseline is 3. The description contributes zero additional parameter meaning, but the schema already does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"A guest's snapshots." is essentially a restatement of the tool name list_snapshots with no verb; it never says it lists or returns anything. It is marginally narrower than the name (scoped to a single guest), but an agent gains no differentiation from siblings like list_backups or guest_details.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when to prefer this over guest_details or how it relates to delete_snapshot. The phrase "a guest's" only implies that a guest context is required, which the schema already enforces via required host/vmid.

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