Skip to main content
Glama

Pull image

pull_image

Pull container images from registries to enable deployment of containerized applications using Podman. This tool retrieves specified images for container management operations.

Instructions

Pull a container image from a registry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageYesImage name with optional tag

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function that implements the pull_image tool logic by executing 'podman pull' on the provided image and returning the result.
    async def pull_image(self, args: Dict[str, Any]) -> Dict[str, Any]:
        image = args.get("image")
        result = run_podman(["pull", image])
        return {"output": f"Pulled image: {image}" if result["success"] else f"Error: {result['stderr']}"}
  • The input schema definition for the pull_image tool, specifying the required 'image' parameter.
    Tool(
        name="pull_image",
        description="Pull a container image from a registry",
        inputSchema={
            "type": "object",
            "properties": {
                "image": {
                    "type": "string",
                    "description": "Image name with optional tag"
                }
            },
            "required": ["image"]
        }
    ),
  • main_b.py:459-472 (registration)
    The dictionary mapping tool names to their handler methods, registering 'pull_image' to self.pull_image.
    tool_handlers = {
        "list_containers": self.list_containers,
        "container_info": self.container_info,
        "start_container": self.start_container,
        "stop_container": self.stop_container,
        "restart_container": self.restart_container,
        "container_logs": self.container_logs,
        "run_container": self.run_container,
        "remove_container": self.remove_container,
        "exec_container": self.exec_container,
        "list_images": self.list_images,
        "pull_image": self.pull_image,
        "container_stats": self.container_stats,
    }
  • main.py:258-261 (handler)
    Alternative implementation using FastMCP decorator, combining handler logic and schema for pull_image tool.
    @mcp.tool(title="Pull image", description="Pull a container image from a registry.")
    def pull_image(image: str = Field(..., description="Image name with optional tag")) -> str:
        result = run_podman(["pull", image])
        return f"Pulled image: {image}" if result["success"] else f"Error: {result['stderr']}"
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't reveal important behavioral aspects: whether it requires authentication to the registry, if it shows progress/output during pull, what happens if the image already exists locally, or potential rate limits. For a network operation with no annotation coverage, this is inadequate.

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 perfectly concise - a single sentence that states exactly what the tool does with zero wasted words. It's front-loaded with the core functionality and doesn't contain any unnecessary information or fluff.

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 that there's an output schema (which handles return values) and 100% schema coverage for the single parameter, the description is minimally complete. However, for a tool that performs network operations and has multiple sibling tools in the container management domain, more context about registry authentication, error conditions, or relationship to other tools would be beneficial.

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 the parameter 'image' is already documented in the schema. The description doesn't add any additional semantic context beyond what the schema provides - no examples of image naming conventions, registry URLs, or tag formats. Baseline 3 is appropriate when the schema does the documentation work.

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 ('container image from a registry'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_images' or 'run_container' which might also involve images, leaving room for ambiguity in tool selection.

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' (to check existing images) and 'run_container' (which might pull images automatically), there's no indication of prerequisites, timing, or when to choose pull_image over other options.

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/kunwarmahen/podman-mcp-server'

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