Skip to main content
Glama
Swartdraak

Docker MCP Server

by Swartdraak

create_container

Create a new Docker container by specifying an image, name, command, environment variables, ports, volumes, and configuration settings.

Instructions

Create a new Docker container

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesDocker image name (e.g., 'nginx:latest')
nameNoContainer name
commandNoCommand to run as an array (e.g., ['python', 'app.py'])
entrypointNoEntrypoint as an array (e.g., ['/bin/bash', '-c'])
envNoEnvironment variables as array of KEY=VALUE strings (e.g., ['NODE_ENV=production', 'PORT=3000'])
exposedPortsNoExposed ports as object with port/protocol keys (e.g., {'80/tcp': {}, '443/tcp': {}})
hostConfigNoHost configuration including port bindings and volumes
labelsNoContainer labels as key-value pairs
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states this is a creation operation but doesn't mention whether it requires specific permissions, what happens if a container with the same name exists, whether the container starts automatically, or what the typical response format might be. For a complex mutation tool with 8 parameters, this is inadequate behavioral context.

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 at just 4 words, front-loading the essential purpose without any wasted words. While this brevity comes at the cost of completeness, as a standalone statement it's efficiently structured.

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?

For a complex container creation tool with 8 parameters, no annotations, no output schema, and multiple sibling tools, the description is severely incomplete. It doesn't address behavioral aspects, usage context, or provide any guidance beyond the basic purpose, leaving significant gaps for an agent trying to use this tool effectively.

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?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with detailed descriptions for all 8 parameters. The baseline score of 3 reflects that the schema does the heavy lifting, though the description could have provided higher-level context about how parameters relate or typical usage patterns.

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 'Create a new Docker container' clearly states the verb ('create') and resource ('Docker container'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'run_container', which appears to serve a similar function, leaving some ambiguity about when to use one versus the other.

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 like 'run_container' or other container management tools. There's no mention of prerequisites, typical use cases, or constraints that would help an agent select this tool appropriately from among the 11 sibling tools available.

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/Swartdraak/Docker-MCP'

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