Nemeton MCP

Overview Schema Source Related Servers Discussions Admin

import_vm

Import a virtual machine from a bundle file. Provide the path to the VM bundle to restore or add it to your local environment.

Instructions

Import a VM from a bundle.

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": {
      "path": "<path>"
    },
    "name": "import_vm"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path to the VM bundle

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It does not mention side effects (e.g., whether it creates a new VM or overwrites), idempotency, error conditions (e.g., invalid path), or resource requirements. The minimal description leaves the agent uninformed about the tool's behavior.

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, straightforward sentence with zero wasted words. It is optimally concise for a tool with one parameter.

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 the tool likely performs a complex operation (importing a VM), the description omits crucial context: return values (success/failure), optional parameters, and behavioral guarantees. The lack of annotations further degrades completeness.

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 coverage is 100% for the single parameter, and the description adds no additional semantics beyond 'from a bundle,' which is already implied by the parameter description. The baseline of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the verb 'Import' and the resource 'VM', and adds 'from a bundle' which distinguishes it from siblings like create_vm and clone_vm. However, it lacks nuance about what importing exactly entails (e.g., creating a new VM vs overlaying).

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 is provided on when to use this tool vs alternatives like export_vm or create_vm. There is no mention of prerequisites (e.g., does the bundle need to already reside on the system?) or scenarios where import is preferred.

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