Skip to main content
Glama
Sign In
Homelab MCP Server

Homelab MCP Server

by washyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clone_proxmox_vm

Create a new VM or container by cloning an existing one on a Proxmox node. Supports full and linked clones for QEMU and LXC.

Instructions

Clone a VM or container to create a new one

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": {
      "node": "<node>",
      "vmid": "<vmid>",
      "new_vmid": "<new_vmid>"
    },
    "name": "clone_proxmox_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoFull clone (true) or linked clone (false)
hostNoProxmox host (optional)
nameNoNew VM name (optional)
nodeYesNode name
vmidYesSource VM/Container ID
vm_typeNoType: 'qemu' for VM or 'lxc' for containerqemu
new_vmidYesNew VM/Container ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already indicate readOnly=false, destructiveHint=false. Description adds no extra behavioral context such as resource consumption, dependency on original, or execution time.

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?

One short sentence clearly stating purpose. No wasted words, directly front-loaded.

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?

Given lack of output schema and moderate parameter count (7), the description should mention return value, status, or whether the operation is synchronous. It does not, leaving agents uninformed about the result.

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 covers all 7 parameters with descriptions. The tool description does not add any parameter-specific details beyond the schema, so baseline score of 3 applies.

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?

Description clearly states the tool clones a VM or container to create a new one. This verb+resource combination distinguishes it from sibling 'create' tools which build from scratch.

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?

No guidance on when to clone vs create, or when to use linked vs full clone. No mention of prerequisites or alternatives.

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