Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

list_backups

Read-onlyIdempotent

List a Proxmox guest's backups newest first by host and VMID, including backups of a guest deleted since by its old ID.

Instructions

A guest's backups, newest first — also of a guest deleted since, by its old ID.

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_backups"
  }
}

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

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's contribution is the deterministic ordering ('newest first') and the notable behavior that a guest deleted since can still be queried by its old ID. It says nothing about result size, pagination, or what fields each backup entry carries, and there is no output schema to fill that gap.

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?

A single front-loaded sentence identifies the resource, the ordering, and the edge case with no filler. Nothing repeats the annotations or the schema, and the em-dash clause is used efficiently for the deleted-guest caveat.

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?

For a two-required-parameter read tool with full annotation coverage and no output schema, the description covers what is returned, how it is ordered, and the deleted-guest case. Only volume/pagination expectations for a list operation are missing, a minor gap given the tool's simplicity.

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 100% so the baseline is 3, and the description earns an extra point by extending vmid semantics: the ID may refer to a guest that has since been deleted. That is meaning not present in the schema text ('The guest's ID (VMID)'), though the host/vmid relationship is still left implicit.

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 names the resource (a guest's backups) and its ordering (newest first), which is enough to separate it from list_backup_jobs and delete_backup at a glance. It never states the verb explicitly, relying on the tool name 'list_backups', but the intent is unambiguous.

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?

Usage is implied by the content rather than stated: it tells you this returns backups for one guest and handles the deleted-guest case by old ID. It does not say when to prefer list_backup_jobs (schedules/jobs) over this tool, nor any prerequisites beyond the host/vmid pair.

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