Skip to main content
Glama

container_status

Check if the Kali Linux Docker container is running to verify environment availability for security testing tools.

Instructions

Check the status of the Kali Linux Docker container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The container_status tool handler, which calls docker.getStatus() and formats the output.
    server.tool(
      "container_status",
      "Check the status of the Kali Linux Docker container.",
      {},
      async () => {
        try {
          const status = await docker.getStatus();
          return {
            content: [{ type: "text", text: JSON.stringify(status, null, 2) }],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to get status: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • The function registerContainerTools registers the container_status tool with the MCP server.
    export function registerContainerTools(
      server: McpServer,
      docker: DockerManager
    ) {
      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,
            };
          }
        }
      );
    
      server.tool(
        "container_stop",
        "Stop and remove the Kali Linux Docker container.",
        {},
        async () => {
          try {
            const message = await docker.stopContainer();
            return { content: [{ type: "text", text: message }] };
          } catch (err) {
            return {
              content: [
                {
                  type: "text",
                  text: `Failed to stop container: ${err instanceof Error ? err.message : String(err)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
    
      server.tool(
        "container_status",
        "Check the status of the Kali Linux Docker container.",
        {},
        async () => {
          try {
            const status = await docker.getStatus();
            return {
              content: [{ type: "text", text: JSON.stringify(status, null, 2) }],
            };
          } catch (err) {
            return {
              content: [
                {
                  type: "text",
                  text: `Failed to get status: ${err instanceof Error ? err.message : String(err)}`,
                },
              ],
              isError: true,
            };
          }
        }
      );
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states 'Check the status' without addressing auth requirements, error handling, or side effects.

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?

Single sentence conveys the purpose without unnecessary words. Perfectly concise for a simple tool.

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?

No output schema, and the description does not explain what the status response contains. The tool is simple but contextually incomplete without return format details.

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 tool has no parameters, and schema coverage is 100%. The description does not add parameter-specific meaning, but baseline is 4 for zero-parameter tools.

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 uses specific verb 'Check' and resource 'status of the Kali Linux Docker container'. It clearly distinguishes from sibling tools like container_start and container_stop.

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 explicit guidance on when to use or avoid this tool. It does not mention alternatives or conditions, leaving the agent to infer from the name and siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.