Skip to main content
Glama
sandraschi

virtualization-mcp

sandbox_management

Manage Docker-based sandboxes for safe, isolated code execution. Supports ephemeral containers and persistent sessions with file operations.

Instructions

Docker-based code sandbox management for safe, isolated code execution.

Requires Docker Desktop running on the host. Two execution modes:

  • Ephemeral: throwaway container, auto-removed after run (execute_code, execute_file)

  • Stateful: persistent session, state preserved between calls (session_*)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform. One of: --- EPHEMERAL (throwaway containers) --- - "execute_code": Run code snippet. Requires: code. Optional: language, timeout, network_enabled - "execute_file": Run a host file. Requires: host_path. Optional: language, timeout, network_enabled --- STATEFUL SESSIONS (persistent containers) --- - "session_create": Create session. Optional: image, sandbox_name - "session_run": Run command in session. Requires: sandbox_id, command - "session_write_file": Write file to session. Requires: sandbox_id, container_path, content - "session_read_file": Read file from session. Requires: sandbox_id, container_path - "session_list": List active sessions. No extra args needed. - "session_destroy": Remove session. Requires: sandbox_id
codeNoCode string to execute (for execute_code)
languageNo"python" | "javascript" | "bash" (default: python)python
host_pathNoAbsolute Windows path to file (for execute_file)
timeoutNoMax execution seconds (default: 30)
network_enabledNoAllow outbound network in container (default: False)
sandbox_idNoSession ID from session_create (for session_* actions)
imageNoDocker image for session_create (default: python:3.13-slim)python:3.13-slim
sandbox_nameNoOptional container name for session_create
commandNoShell command for session_run
container_pathNoPath inside container for file operations
contentNoFile content string for session_write_file

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description effectively conveys behavioral traits: isolated execution, auto-removal for ephemeral, persistence for stateful sessions. It adds value by outlining the two execution modes and the requirement for Docker.

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 extremely concise, using just a few sentences to convey purpose, prerequisites, and execution modes. It front-loads the core function and avoids unnecessary details.

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

Completeness4/5

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

Given the tool's complexity (12 parameters, many actions) and the presence of an output schema, the description provides sufficient high-level context. It covers the overall purpose, prerequisites, and mode classification, but could include a note on error behavior.

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 description coverage is 100%, so the baseline is 3. The description provides high-level context for parameters (like grouping actions) but does not add new semantic info beyond the already detailed schema descriptions.

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 it is for Docker-based code sandbox management, specifying safe isolated execution. It explicitly distinguishes from sibling tools like info_tools or network_management by focusing on code execution and session management.

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 provides a key prerequisite (Docker Desktop running) and explains when to use ephemeral vs stateful modes. However, it does not explicitly mention when not to use the tool or list alternatives among siblings, though the context is clear.

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