Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

take_snapshot

Capture a Proxmox guest's current state as a named snapshot for rollback or recovery, with a reason logged for approval.

Instructions

Take a snapshot of a guest.

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

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
nameYes
vmidYesThe guest's ID (VMID).
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent mutation, but the description adds no behavioral context. It does not explain what the snapshot includes, whether the guest must be running, or how the required reason and approval flow affect invocation.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted wording. Its brevity is efficient, though it leaves the agent with little structure or context beyond the core action.

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 mutation tool with five parameters, four required, and no output schema. The description is too sparse for that complexity: it does not cover parameter roles, guest-state requirements, approval/logging implications, or alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, with host, vmid, and reason described in the schema but name and description undocumented. The tool description adds no parameter meaning beyond saying the target is a guest, so it does not compensate for the remaining schema gaps.

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 states a specific verb and resource: "Take a snapshot" of a "guest." It is clear enough to identify the action, though it does not distinguish this tool from nearby alternatives such as delete_snapshot or rollback_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?

The description gives no guidance about when to use this tool versus alternatives like backup_now or rollback_snapshot. It also omits prerequisites, guest-state constraints, and any when-not-to-use conditions, leaving usage only implied by the name.

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