Skip to main content
Glama

list_containers

Retrieve a list of Docker containers to monitor and manage running or all container instances for system oversight.

Instructions

List all Docker containers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoShow all containers (default shows just running)

Implementation Reference

  • The handler function for 'list_containers' tool. Executes 'docker ps' (with optional -a for all containers), parses tabular output into JSON array of {id, image, status, name}, returns as text content.
    private async listContainers(args: ContainerArgs) {
      const showAll = args?.all === true ? '-a' : '';
      const { stdout } = await execAsync(`docker ps ${showAll} --format "{{.ID}}\\t{{.Image}}\\t{{.Status}}\\t{{.Names}}"`);
      
      const containers = stdout.trim().split('\n')
        .filter(line => line.trim() !== '')
        .map(line => {
          const [id, image, status, name] = line.split('\t');
          return { id, image, status, name };
        });
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(containers, null, 2),
          },
        ],
      };
    }
  • src/index.ts:69-81 (registration)
    Tool registration in ListToolsRequestHandler response, including name, description, and input schema.
    {
      name: 'list_containers',
      description: 'List all Docker containers',
      inputSchema: {
        type: 'object',
        properties: {
          all: {
            type: 'boolean',
            description: 'Show all containers (default shows just running)',
          },
        },
      },
    },
  • TypeScript interface defining the input arguments for the list_containers tool.
    interface ContainerArgs {
      all?: boolean;
    }
  • src/index.ts:189-190 (registration)
    Switch case in CallToolRequestHandler that routes 'list_containers' calls to the handler function.
    case 'list_containers':
      return await this.listContainers(request.params.arguments as unknown as ContainerArgs);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List') but doesn't describe what the output looks like (e.g., format, fields), whether it's paginated, or any side effects. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 that front-loads the core purpose without any wasted words. It's appropriately sized for a simple tool with one parameter and clear schema documentation. Every part of the sentence earns its place by directly stating the tool's function.

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 lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what the output contains (e.g., container IDs, statuses), how results are formatted, or any behavioral nuances. For a tool that likely returns structured data, this omission leaves the agent without crucial context for interpreting results.

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 input schema has 100% description coverage, with one parameter ('all') fully documented in the schema. The description adds no additional parameter semantics beyond implying a listing action. Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description doesn't enhance parameter understanding but doesn't need to compensate for gaps.

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 verb ('List') and resource ('all Docker containers'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'list_images' or 'remove_container', but the core action is unambiguous. The description avoids tautology by specifying what is being listed rather than just restating the tool name.

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 'list_images' or 'remove_container'. It doesn't mention prerequisites, context for usage, or exclusions. The agent must infer usage from the tool name alone, which is insufficient for optimal tool selection in a multi-tool environment.

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