Skip to main content
Glama
BenjaminDuthe

Proxmox MCP Server

list_snapshots

List all snapshots for a specified Proxmox VM or LXC container by providing the node and VMID.

Instructions

Liste les snapshots d'une VM ou conteneur

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesNom du nœud Proxmox
typeNoType: qemu (VM) ou lxc (conteneur)qemu
vmidYesID de la VM/LXC
Behavior2/5

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

Aucune annotation fournie. La description ne détaille pas le comportement (lecture seule, permissions nécessaires, format de retour). Seul le mot 'liste' suggère une opération non destructive, mais ce n'est pas explicite.

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?

Une phrase courte, sans mots superflus, l'information essentielle est en tête. Parfaitement concise.

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?

Avec 3 paramètres, pas de schéma de sortie et pas d'annotations, la description est trop minimaliste. Elle ne précise pas le format de sortie, ni comment interpréter les snapshots listés. Insuffisante pour un agent IA.

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?

La couverture du schéma est de 100%, donc la description n'ajoute pas de valeur sémantique au-delà du schéma. Baseline de 3 atteint.

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?

Le verbe 'liste' et la ressource 'snapshots' sont clairs. Le contexte 'VM ou conteneur' précise la portée. La description se distingue bien des outils frères comme create_snapshot ou delete_snapshot.

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?

Aucune indication sur quand utiliser cet outil par rapport aux alternatives (create_snapshot, rollback_snapshot, etc.). Pas de mention des prérequis ou des cas d'usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BenjaminDuthe/proxmox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server