Skip to main content
Glama

pull_image

Pull Docker images from registries to your local machine for container deployment and management.

Instructions

Pull a Docker image from a registry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesImage name (e.g. "nginx:latest")

Implementation Reference

  • The handler function that implements the logic for pulling a Docker image using the 'docker pull' command. It validates the image argument and returns the command output.
    private async pullImage(args: ImageArgs) {
      if (!args.image) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Image parameter is required'
        );
      }
      
      const { stdout } = await execAsync(`docker pull ${args.image}`);
      
      return {
        content: [
          {
            type: 'text',
            text: stdout.trim(),
          },
        ],
      };
    }
  • src/index.ts:169-182 (registration)
    The registration of the 'pull_image' tool in the list of tools provided to the MCP client, including its name, description, and input schema.
    {
      name: 'pull_image',
      description: 'Pull a Docker image from a registry',
      inputSchema: {
        type: 'object',
        properties: {
          image: {
            type: 'string',
            description: 'Image name (e.g. "nginx:latest")',
          },
        },
        required: ['image'],
      },
    },
  • TypeScript interface defining the input arguments for the pull_image tool.
    interface ImageArgs {
      image: string;
    }
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. While 'pull' implies a network operation to fetch an image, it lacks details on permissions needed, whether it overwrites existing images, error handling (e.g., for missing images), or performance aspects like timeouts. This leaves significant gaps for safe and effective use.

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, clear sentence with zero wasted words, making it easy to parse and front-loaded with essential information. It efficiently conveys the core action without unnecessary elaboration, earning full marks for brevity and structure.

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 insufficient for a tool that performs a network operation. It doesn't cover behavioral traits like authentication needs, rate limits, or what happens on success/failure, leaving the agent with incomplete context to invoke it reliably in complex scenarios.

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 'image' well-documented in the schema as 'Image name (e.g., "nginx:latest")'. The description adds no additional semantic context beyond what the schema provides, such as registry defaults or tag conventions, meeting the baseline for adequate but not enhanced parameter understanding.

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 ('pull') and resource ('Docker image from a registry'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_images' or 'run_container' which also involve Docker images, leaving room for potential confusion about when to choose this specific tool.

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. With siblings like 'list_images' (for viewing existing images) and 'run_container' (which might implicitly pull images), there's no indication of prerequisites, typical use cases, or distinctions that would help an agent select this tool appropriately in context.

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