Skip to main content
Glama

image_build

Build a Docker image from a Dockerfile using the classic builder. Supports simple single-platform builds from a local context.

Instructions

Build an image from a Dockerfile using the daemon's classic builder.

Use this for simple single-platform builds from a local context. For multi-platform builds, BuildKit cache export/import, or advanced build features prefer buildx_build. path must be a directory accessible on the host running this server (it is the build context sent to the daemon). dockerfile is relative to path; omit to use the default Dockerfile.

args: path - Build context directory path on the server host tag - Name and optional tag in "name:tag" format to apply to the built image quiet - Suppress verbose build output (final image id still returned) nocache - Ignore the layer cache and rebuild all layers rm - Remove intermediate containers on success (default True) pull - Always pull a newer version of each FROM base image before building forcerm - Remove intermediate containers even on build failure dockerfile - Dockerfile filename relative to path (default: "Dockerfile") buildargs - Build-time variables passed as --build-arg; dict of str→str container_limits - Resource limits for the build container, e.g. {"memory": 134217728} shmsize - Size of /dev/shm in bytes for build steps that need shared memory labels - Labels to set on the resulting image (dict of str→str) cache_from - List of image references to use as layer cache sources target - Stop at this named build stage (multi-stage Dockerfiles) network_mode - Network mode for RUN instructions during build (e.g. "host", "none") squash - Squash all new layers into one (experimental; requires daemon flag) extra_hosts - Additional /etc/hosts entries during build; dict of hostname→ip platform - Target platform, e.g. "linux/amd64" (single platform only; use buildx for multi) isolation - Windows isolation technology ("default", "process", "hyperv") use_config_proxy - Forward proxy env vars from Docker client config to build returns: dict - The built image's full inspect payload (as docker inspect)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rmNo
tagNo
pathNo
pullNo
quietNo
labelsNo
squashNo
targetNo
forcermNo
nocacheNo
shmsizeNo
platformNo
buildargsNo
isolationNo
cache_fromNo
dockerfileNo
extra_hostsNo
network_modeNo
container_limitsNo
use_config_proxyNo
Behavior4/5

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

Annotations readOnlyHint=false and destructiveHint=false indicate a mutating but not destructive operation. The description adds valuable behavioral context beyond annotations: it uses the classic builder, requires host-accessible path, defaults for rm/dockerfile, quiet suppresses output but returns image id, squash is experimental, and platform is single-only. It does not explicitly mention long-running behavior or network pull implications, so not a 5.

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?

Although long, the description is well-structured: opening summary, usage guidance, path/dockerfile clarification, then a complete parameter list, and a returns note. Every sentence adds value, and information is front-loaded with the most important guidance before parameter details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (20 params, nested objects, no output schema), the description is remarkably complete. It covers the return value, all parameters, default behaviors, and differentiates from the primary sibling. No essential information appears missing for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for parameter semantics. It provides a detailed args list explaining each of the 20 parameters, including types, defaults, behaviors, and examples (e.g., buildargs dict str→str, container_limits example, shmsize meaning). This fully compensates for the schema's lack of descriptions.

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 clearly states the verb+resource: 'Build an image from a Dockerfile using the daemon's classic builder.' It also distinguishes from the sibling tool buildx_build, saying to prefer that for multi-platform or advanced builds, so it uniquely identifies this tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool versus alternatives: 'Use this for simple single-platform builds from a local context. For multi-platform builds, BuildKit cache export/import, or advanced build features prefer buildx_build.' Provides clear context on input requirements (host-accessible path).

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/L337-org/docker-mcp'

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