Skip to main content
Glama
ConnorBoetig-dev

Unrestricted Development MCP Server

docker_stop

Stop running Docker containers by name or ID to halt application processes and free system resources for development environments.

Instructions

Stop one or more running containers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
containersYesContainer name(s) or ID(s)
timeoutNoSeconds to wait before killing container
cwdNoWorking directory

Implementation Reference

  • The main handler function for the docker_stop tool that constructs and executes the 'docker stop' command via the executeDockerCommand helper.
    export async function dockerStop(args: z.infer<typeof dockerStopSchema>): Promise<ToolResponse> {
      const containers = Array.isArray(args.containers) ? args.containers.join(' ') : args.containers;
      const timeoutFlag = args.timeout ? `-t ${args.timeout}` : '';
      return executeDockerCommand(`docker stop ${timeoutFlag} ${containers}`.trim(), args.cwd);
    }
  • Zod input validation schema for the docker_stop tool.
    export const dockerStopSchema = z.object({
      containers: z.union([z.string(), z.array(z.string())]).describe('Container name(s) or ID(s)'),
      timeout: z.number().optional().describe('Seconds to wait before killing container'),
      cwd: z.string().optional().describe('Working directory')
    });
  • MCP tool registration definition in dockerTools array (used for tool listing), including name, description, and JSON input schema.
    {
      name: 'docker_stop',
      description: 'Stop one or more running containers',
      inputSchema: {
        type: 'object',
        properties: {
          containers: {
            oneOf: [
              { type: 'string' },
              { type: 'array', items: { type: 'string' } }
            ],
            description: 'Container name(s) or ID(s)'
          },
          timeout: { type: 'number', description: 'Seconds to wait before killing container' },
          cwd: { type: 'string', description: 'Working directory' }
        },
        required: ['containers']
      }
    },
  • src/index.ts:459-462 (registration)
    Dispatch/registration logic in the main CallToolRequest handler that validates arguments with dockerStopSchema and calls the dockerStop handler function.
    if (name === 'docker_stop') {
      const validated = dockerStopSchema.parse(args);
      return await dockerStop(validated);
    }
  • Shared helper function used by all Docker tools (including dockerStop) to execute docker commands and format responses.
    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 the full burden of behavioral disclosure. While 'Stop' implies a state change (from running to stopped), the description doesn't mention important behavioral traits: whether this is reversible (it is via 'docker_start'), what happens to container data (typically preserved), permission requirements, or error conditions. 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 states the core functionality without unnecessary words. It's appropriately sized for a straightforward tool and front-loads the essential information ('Stop one or more running containers').

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'stop' means operationally, what the expected outcome is, error scenarios, or how this differs from related tools. The agent would need to rely heavily on external Docker knowledge rather than the description alone.

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 schema has 100% description coverage, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's in the schema (e.g., it doesn't explain format expectations for container names/IDs, typical timeout values, or why 'cwd' is relevant). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Stop') and resource ('one or more running containers'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'docker_restart' or 'docker_rm', which would require more specific language about what 'stop' means versus those alternatives.

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 'docker_restart' (which stops and starts) or 'docker_rm' (which removes containers). It also doesn't mention prerequisites (e.g., containers must be running) or typical use cases, leaving the agent to infer usage from context alone.

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