Skip to main content
Glama

stop_container

Stop a running Docker container by specifying its ID or name to halt processes and free system resources.

Instructions

Stop a running Docker container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContainer ID or name

Implementation Reference

  • The core handler function that executes the Docker container stop operation using Dockerode API. It gets the container by ID and calls the stop() method.
    export async function stopContainer(id: string): Promise<string> {
      const container = docker.getContainer(id);
      await container.stop();
      return `Container ${id} stopped`;
    }
  • src/index.ts:80-88 (registration)
    MCP tool registration for 'stop_container' with description, input schema using Zod, and handler that delegates to the stopContainer function.
    server.tool(
      "stop_container",
      "Stop a running Docker container.",
      { id: z.string().describe("Container ID or name") },
      async ({ id }) => {
        const result = await stopContainer(id);
        return { content: [{ type: "text", text: result }] };
      },
    );
  • Zod schema defining the input parameter 'id' as a required string with description for the stop_container tool.
    { id: z.string().describe("Container ID or name") },
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. It states the action but doesn't explain what 'stop' entails (e.g., graceful shutdown vs. force, state persistence, error handling, or permissions required). This leaves significant gaps in understanding the tool's behavior beyond the basic operation.

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 with zero waste, clearly front-loading the core action. It's appropriately sized for a simple tool, making it easy to parse without unnecessary elaboration.

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 details on behavioral traits, error cases, or return values, which are crucial for safe and effective use in a Docker management context.

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 description coverage is 100%, with the single parameter 'id' documented as 'Container ID or name'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate since 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 action ('Stop') and resource ('a running Docker container'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'restart_container' or 'remove_container' beyond the basic verb, missing an opportunity to clarify its specific role in the container lifecycle.

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?

No guidance is provided on when to use this tool versus alternatives like 'restart_container' or 'remove_container'. The description assumes the agent knows the context of stopping versus other container operations, offering no explicit when/when-not instructions or prerequisites for a running container.

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

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