Skip to main content
Glama
mustafaTokmak

container-mcp

Run container

run_container

Run containerized applications in isolated VMs on Mac. Supports detached execution or waiting for output, with configurable resources, ports, mounts, and environment variables.

Instructions

Run a container inside its own lightweight VM. By default runs detached and returns the container ID. Pass wait: true to run to completion and return the container's output (10 minute limit). Mount sources must be inside the allowed host paths. Default CPU/memory limits are applied unless overridden.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNoEnvironment variables
cpusNoCPU limit, e.g. '4'
nameNoOptional container name
waitNoRun to completion and return the container's output instead of its ID (10 minute limit)
imageYesImage reference, e.g. alpine:latest
portsNoPublish container ports to the host
memoryNoMemory limit, e.g. '4g'
mountsNo
commandNoCommand and arguments to run
networkNoAllow outbound network access (default: denied unless CONTAINER_MCP_ALLOW_NETWORK is set)
workdirNoWorking directory inside the container
Behavior4/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 discloses key behaviors: detached by default, wait mode with 10-minute limit, mount path restrictions, and default CPU/memory limits. It does not cover cleanup behavior or error states, but adds significant context beyond a basic 'runs a container'.

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 four sentences, all essential and front-loaded with the primary action. No superfluous words, and each sentence adds distinct information (detached mode, wait option, mount rules, resource defaults).

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 (11 parameters, nested objects, no output schema), the description covers key aspects: run mode, output handling, mount constraints, and default resources. It could mention that the container remains running after returning ID, and possibly error handling, but overall it is sufficient for an agent to understand the tool's behavior.

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

Parameters4/5

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

Schema coverage is high (91%), so baseline is 3. The description adds value by clarifying that mount sources must be in allowed paths, default limits apply unless overridden, and the wait parameter's behavior. This provides context beyond the 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 that it runs a container in its own lightweight VM, and distinguishes from sibling tools like list_containers, container_logs, etc., which are for managing existing containers. The purpose is specific and unambiguous.

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 explains the default detached behavior, the wait option for completion, mount constraints, and default resource limits. It provides clear context on when to use the tool, but does not explicitly mention when not to use it or alternative tools like exec_in_container for running commands in existing containers.

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/mustafaTokmak/container-mcp'

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