Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clone_container

Clone an existing LXC container or template to a new ID, with options for full copy, target node, and storage.

Instructions

Clone an existing LXC container or template.

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

Input Schema

NameRequiredDescriptionDefault
fullNo
nameNo
nodeYes
vmidYes
newidYes
targetNo
storageNo
hostnameNo
snapnameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Clone an existing LXC container or template' without revealing whether it performs a full or linked clone, whether the source must be stopped, or what side effects occur. This adds minimal behavioral context beyond the tool's name.

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?

The description is a single, concise sentence that front-loads the core action. It is efficient and directly states the tool's purpose without unnecessary verbiage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, 3 required), no annotations, and no output schema, the description is severely incomplete. It omits critical details about required inputs, clone behavior, target node, storage, and potential consequences, making it inadequate for safe and correct invocation.

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

Parameters1/5

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

With 0% schema description coverage and no explanation of any parameters in the description, the agent must infer meanings from parameter names alone. The description adds no semantic value for the 9 parameters, making correct parameter usage uncertain.

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?

The description clearly states the tool's action ('Clone') and the resource ('existing LXC container or template'). It also implicitly distinguishes from sibling 'clone_vm' by specifying LXC containers, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as 'clone_vm' or 'template_container'. It does not mention prerequisites, exclusions, or typical scenarios, leaving the agent without context for tool selection.

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