Skip to main content
Glama
ConnorBoetig-dev

Unrestricted Development MCP Server

docker_images

List Docker images with filtering options to manage container environments and identify available images for development workflows.

Instructions

List Docker images

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoFilter images (e.g., "reference=node:*")
allNoShow all images (default hides intermediate)
formatNoOutput formattable
cwdNoWorking directory

Implementation Reference

  • The main handler function that constructs and executes the 'docker images' command using the shared executeDockerCommand helper, based on input arguments.
    export async function dockerImages(args: z.infer<typeof dockerImagesSchema>): Promise<ToolResponse> {
      const allFlag = args.all ? '-a' : '';
      const filterFlag = args.filter ? `--filter "${args.filter}"` : '';
      const formatFlag = args.format === 'json'
        ? '--format "{{json .}}"'
        : '--format "table {{.Repository}}\\t{{.Tag}}\\t{{.ID}}\\t{{.Size}}"';
    
      return executeDockerCommand(`docker images ${allFlag} ${filterFlag} ${formatFlag}`.trim(), args.cwd);
    }
  • Zod schema for validating input arguments to the docker_images tool.
    export const dockerImagesSchema = z.object({
      filter: z.string().optional().describe('Filter images (e.g., "reference=node:*")'),
      all: z.boolean().optional().default(false).describe('Show all images (default hides intermediate)'),
      format: z.enum(['table', 'json']).optional().default('table').describe('Output format'),
      cwd: z.string().optional().describe('Working directory')
    });
  • MCP tool metadata definition for 'docker_images' included in the exported dockerTools array used for tool listing.
    {
      name: 'docker_images',
      description: 'List Docker images',
      inputSchema: {
        type: 'object',
        properties: {
          filter: { type: 'string', description: 'Filter images (e.g., "reference=node:*")' },
          all: { type: 'boolean', default: false, description: 'Show all images (default hides intermediate)' },
          format: { type: 'string', enum: ['table', 'json'], default: 'table', description: 'Output format' },
          cwd: { type: 'string', description: 'Working directory' }
        }
      }
    },
  • src/index.ts:475-478 (registration)
    Dispatch logic in the main MCP CallToolRequest handler that routes calls to docker_images by validating arguments and invoking the handler function.
    if (name === 'docker_images') {
      const validated = dockerImagesSchema.parse(args);
      return await dockerImages(validated);
    }
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 for behavioral disclosure. 'List Docker images' implies a read-only operation but doesn't specify whether it shows local/remote images, default sorting, pagination, or error behavior. For a tool with 4 parameters and no annotation coverage, this is a significant gap in transparency about how the tool actually behaves.

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 perfectly concise three-word phrase that front-loads the essential action. Every word earns its place with zero waste or redundancy. It follows the principle of being appropriately sized for a simple listing 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?

Given 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns (e.g., image IDs, tags, sizes), how results are formatted, or behavioral aspects like error handling. For a tool with this complexity level, the description should provide more context about the operation.

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%, so all parameters are documented in the schema. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'List Docker images' clearly states the verb ('List') and resource ('Docker images'), making the purpose immediately understandable. It distinguishes from obvious siblings like docker_build or docker_pull, though it doesn't explicitly differentiate from docker_ps (which lists containers, not images). The description is specific but could be slightly more precise about scope.

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. It doesn't mention when to use docker_images versus docker_ps (for containers) or docker_inspect (for detailed image info), nor does it specify prerequisites like needing Docker installed or running. The agent must infer usage from the name alone.

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/ConnorBoetig-dev/mcp2'

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