Skip to main content
Glama

container_start

Start the Kali Linux Docker container to enable security testing tools like nmap, sqlmap, and metasploit. Required before executing any commands in the environment.

Instructions

Start the Kali Linux Docker container. Must be called before running any commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration for "container_start" in src/tools/container.ts.
    server.tool(
      "container_start",
      "Start the Kali Linux Docker container. Must be called before running any commands.",
      {},
      async () => {
        try {
          const message = await docker.startContainer();
          return { content: [{ type: "text", text: message }] };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to start container: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Implementation handler for "container_start" in DockerManager class within src/docker-manager.ts.
    async startContainer(): Promise<string> {
      // Check if container already exists
      const existing = await this.getContainer();
      if (existing) {
        const info = await existing.inspect();
        if (info.State.Running) {
          return "Kali container is already running.";
        }
        // Container exists but stopped — start it
        await existing.start();
        return "Kali container started.";
      }
    
      // Check if image exists
      if (!(await this.imageExists())) {
        return "Kali Docker image not found. Please build it first: cd docker && docker-compose build";
      }
    
      // Create and start a new container
      const container = await this.docker.createContainer({
        Image: IMAGE_NAME,
        name: CONTAINER_NAME,
        Tty: true,
        OpenStdin: true,
        WorkingDir: "/workspace",
        HostConfig: {
          NetworkMode: "bridge",
        },
      });
      await container.start();
      return "Kali container created and started.";
    }
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 action without behavioral details. It doesn't disclose whether this requires specific permissions, what happens if the container is already running (e.g., error, idempotency), timeouts, or side effects. The description adds minimal context beyond the basic action, leaving significant gaps for a mutation tool.

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 two concise sentences with zero waste. The first sentence states the core action, and the second provides critical usage context. It's front-loaded with the main purpose and efficiently structured without unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 0 parameters, the description is minimally complete for a simple start operation. It covers the what and when but lacks behavioral transparency (e.g., error conditions, idempotency) and output details. For a mutation tool with siblings like container_status, more context on state changes would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing on the tool's purpose instead. This meets the baseline for zero-parameter tools, as there's nothing to compensate for.

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 resource ('Kali Linux Docker container'), making the purpose immediately understandable. It distinguishes from siblings like container_stop or container_status by specifying the start operation. However, it doesn't explicitly contrast with other container operations beyond the implied opposite of stop.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear contextual guidance with 'Must be called before running any commands,' indicating a prerequisite relationship with execute_command and other operational tools. It implicitly suggests when to use (before command execution) but doesn't explicitly mention alternatives like container_status for checking state or warn against redundant calls if already running.

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/Hannes221/kali-mcp'

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