Skip to main content
Glama
sandraschi

virtualization-mcp

network_management

Manage virtual networks and adapters: create or remove host-only networks, list networks and adapters, and configure VM network adapter settings.

Instructions

Comprehensive network management portmanteau tool.

This tool consolidates all network operations into a single interface. Use the 'action' parameter to specify which operation to perform. Different actions require different parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe operation to perform. Must be one of: - "list_networks": List all host-only networks (no other parameters required) - "create_network": Create a host-only network (requires: network_name) - "remove_network": Remove a host-only network (requires: network_name) - "list_adapters": List network adapters for a VM (requires: vm_name) - "configure_adapter": Configure network adapter for a VM (requires: vm_name, adapter_slot, network_type)
network_nameNoName of the host-only network (required for create_network, remove_network, configure_adapter)
vm_nameNoName of the virtual machine (required for list_adapters, configure_adapter)
adapter_slotNoNetwork adapter slot number 0-3 (required for configure_adapter)
network_typeNoNetwork type for adapter configuration (required for configure_adapter). Valid values: "nat", "bridged", "hostonly", "internal", "generic", "natnetwork"
ip_addressNoIP address for network configuration (optional for create_network)
netmaskNoNetwork mask for network configuration (optional for create_network)
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions actions but does not disclose behavioral traits such as which actions are destructive (e.g., remove) or require specific permissions. Lacks warnings about side effects.

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 short (two sentences) and to the point. It could be improved by front-loading the most important guidance, but it is still concise and readable.

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

Completeness3/5

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

With an output schema present, the description need not explain return values. However, given the complexity (5 actions, 9 parameters), the description is minimal and does not provide usage examples or clarify parameter dependencies beyond the action enum descriptions.

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 high (78%) and the schema includes detailed descriptions for each action, especially for the 'action' parameter. The description adds little beyond 'Use the action parameter to specify which operation to perform', so it meets the baseline but does not exceed.

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 it is a comprehensive network management tool consolidating all network operations, and lists the actions via the 'action' parameter. It distinguishes from sibling tools which are for other domains (info, sandbox, etc.). However, being a portmanteau tool reduces focus slightly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description instructs to use the 'action' parameter to specify the operation. Since it is the only network tool among siblings, no when-not-to-use is needed, but explicit context is provided.

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/sandraschi/virtualization-mcp'

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