Skip to main content
Glama

stop_container

Stop a running Docker container by specifying its ID or name. This tool halts container execution for management or resource conservation.

Instructions

Stop a running Docker container

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
containerYesContainer ID or name

Implementation Reference

  • The handler function implementing the 'stop_container' tool logic: validates input and executes 'docker stop' command.
    private async stopContainer(args: ContainerActionArgs) {
      if (!args.container) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Container parameter is required'
        );
      }
      
      const { stdout } = await execAsync(`docker stop ${args.container}`);
      
      return {
        content: [
          {
            type: 'text',
            text: stdout.trim(),
          },
        ],
      };
    }
  • Type/interface definition for arguments used in stop_container (and remove_container).
    interface ContainerActionArgs {
      container: string;
      force?: boolean;
    }
  • src/index.ts:138-150 (registration)
    Tool registration in list_tools handler: defines name, description, and input schema for 'stop_container'.
      name: 'stop_container',
      description: 'Stop a running Docker container',
      inputSchema: {
        type: 'object',
        properties: {
          container: {
            type: 'string',
            description: 'Container ID or name',
          },
        },
        required: ['container'],
      },
    },
  • Dispatcher in CallToolRequestSchema handler that invokes the stopContainer method for 'stop_container' tool.
    case 'stop_container':
      return await this.stopContainer(request.params.arguments as unknown as ContainerActionArgs);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether stopping is reversible, if it requires specific permissions, potential side effects (e.g., data persistence), or error conditions (e.g., invalid container ID).

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, front-loaded sentence with zero waste. It efficiently conveys the core purpose without unnecessary words, making it easy to parse quickly.

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 the complexity of a destructive operation (stopping a container) with no annotations and no output schema, the description is incomplete. It lacks critical context like what happens after stopping, return values, or error handling, which are essential for safe tool invocation.

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 the parameter 'container' documented as 'Container ID or name'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 the specific action ('stop') and target resource ('a running Docker container'), distinguishing it from sibling tools like remove_container (deletion) and run_container (starting). It uses precise terminology that aligns with Docker operations.

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., the container must be running), exclusions (e.g., not for stopped containers), or relationships to siblings like list_containers (to identify containers to stop).

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/suvarchal/docker-mcp'

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