Skip to main content
Glama
ConnorBoetig-dev

Unrestricted Development MCP Server

docker_start

Start one or more stopped Docker containers by name or ID to resume their operation in your development environment.

Instructions

Start one or more stopped containers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
containersYesContainer name(s) or ID(s)
cwdNoWorking directory

Implementation Reference

  • Main handler function that constructs and executes the 'docker start' command on specified containers using the executeDockerCommand helper.
    export async function dockerStart(args: z.infer<typeof dockerStartSchema>): Promise<ToolResponse> {
      const containers = Array.isArray(args.containers) ? args.containers.join(' ') : args.containers;
      return executeDockerCommand(`docker start ${containers}`, args.cwd);
    }
  • Zod schema for input validation of docker_start tool parameters (containers and optional cwd).
    export const dockerStartSchema = z.object({
      containers: z.union([z.string(), z.array(z.string())]).describe('Container name(s) or ID(s)'),
      cwd: z.string().optional().describe('Working directory')
    });
  • MCP tool definition/registration in dockerTools array, including name, description, and JSON inputSchema for the docker_start tool.
    {
      name: 'docker_start',
      description: 'Start one or more stopped containers',
      inputSchema: {
        type: 'object',
        properties: {
          containers: {
            oneOf: [
              { type: 'string' },
              { type: 'array', items: { type: 'string' } }
            ],
            description: 'Container name(s) or ID(s)'
          },
          cwd: { type: 'string', description: 'Working directory' }
        },
        required: ['containers']
      }
    },
  • Top-level dispatch handler in MCP server that matches tool name 'docker_start', validates arguments, and invokes the dockerStart function.
    if (name === 'docker_start') {
      const validated = dockerStartSchema.parse(args);
      return await dockerStart(validated);
  • Core helper utility that executes any Docker command via child_process.execAsync, handles output/error formatting, and returns standardized ToolResponse.
    async function executeDockerCommand(command: string, cwd?: string): Promise<ToolResponse> {
      try {
        const { stdout, stderr } = await execAsync(command, {
          cwd: cwd || process.cwd(),
          shell: '/bin/bash',
          maxBuffer: 10 * 1024 * 1024, // 10MB buffer for logs
          timeout: 60000 // 60 second timeout for builds
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                success: true,
                command: command,
                stdout: stdout.trim(),
                stderr: stderr.trim(),
                cwd: cwd || process.cwd()
              }, null, 2)
            }
          ]
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                success: false,
                command: command,
                stdout: error.stdout?.trim() || '',
                stderr: error.stderr?.trim() || error.message,
                exitCode: error.code || 1,
                cwd: cwd || process.cwd()
              }, null, 2)
            }
          ],
          isError: true
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Start') which implies a mutation operation, but doesn't disclose any behavioral traits such as permissions required, whether it's idempotent (what happens if container is already running), error conditions, or what the output looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information. Every word earns its place in this concise formulation.

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 this is a mutation tool with no annotations, no output schema, and multiple sibling tools in the Docker ecosystem, the description is incomplete. It doesn't address behavioral aspects, error handling, or differentiation from similar tools. The agent lacks sufficient context to understand the full implications of using this tool.

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%, with both parameters clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the structured schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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 action ('Start') and target resource ('one or more stopped containers'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like docker_restart (which might restart running containers) or docker_compose_up (which starts services defined in compose files), leaving room for ambiguity in sibling differentiation.

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. It doesn't mention prerequisites (e.g., containers must be stopped), exclusions (e.g., cannot start already running containers), or comparisons to siblings like docker_restart or docker_compose_up. The agent receives no contextual usage information.

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/ConnorBoetig-dev/mcp2'

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