Skip to main content
Glama

restart_container

Restart a Docker container by providing its ID or name to resolve issues or apply configuration changes.

Instructions

Restart a Docker container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContainer ID or name

Implementation Reference

  • The handler function that executes the restart_container tool logic. It uses the Docker API to restart a container by ID and returns a confirmation message.
    export async function restartContainer(id: string): Promise<string> {
      const container = docker.getContainer(id);
      await container.restart();
      return `Container ${id} restarted`;
    }
  • src/index.ts:90-98 (registration)
    Registration of the 'restart_container' MCP tool with the server, including the tool name, description, and handler that calls restartContainer.
    server.tool(
      "restart_container",
      "Restart a Docker container.",
      { id: z.string().describe("Container ID or name") },
      async ({ id }) => {
        const result = await restartContainer(id);
        return { content: [{ type: "text", text: result }] };
      },
    );
  • Input schema for restart_container tool using Zod: validates that 'id' is a required string parameter representing the container ID or name.
    { id: z.string().describe("Container ID or name") },
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Restart' implies a mutation operation, it doesn't disclose whether this requires specific permissions, whether it's reversible, what happens to running processes, or potential side effects. For a mutation tool with zero annotation coverage, this is inadequate behavioral disclosure.

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 wasted words. It's appropriately sized for a simple tool and front-loads the essential information immediately.

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, no output schema, and multiple sibling alternatives, the description is incomplete. It doesn't address behavioral implications, usage context relative to other container tools, or what to expect from the operation. Given the complexity of container management, more guidance is needed.

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 single parameter 'id' documented as 'Container ID or name'. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 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 action ('Restart') and target resource ('a Docker container'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'stop_container' and 'start_container' which could be used in sequence for similar effect, missing explicit 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 like 'stop_container' followed by 'start_container', nor does it mention prerequisites (e.g., container must be running) or exclusions. With multiple sibling container management tools, this lack of comparative context is a significant gap.

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