Skip to main content
Glama

buildx_create

Create a new BuildKit builder for multi-platform builds and cache export. Set it as default or bootstrap immediately.

Instructions

Create a new BuildKit builder instance.

Needed when the default docker driver falls short: multi-platform builds and cache export require a docker-container (or kubernetes/remote) builder. Pass use=True to make it the default for later buildx_build calls (else switch with buildx_use); bootstrap=True starts the builder now rather than on first build. Does not raise on a non-zero CLI exit (a missing buildx plugin or a timeout still raises) - inspect returncode/stderr in the result.

Args: name: Name for the new builder (defaults to a generated name) driver: BuildKit driver (e.g. "docker-container", "kubernetes", "remote") driver_opts: Driver-specific options (each becomes --driver-opt KEY=VALUE) use: Set the new builder as the current one bootstrap: Boot the builder immediately platforms: Platforms the builder advertises config: Path to a buildkitd config file (copied to the target host if no local plugin); passed as --buildkitd-config, so this argument needs buildx >= 0.17 node_name: Node name within the builder (for multi-node builders) append: Append a node to an existing builder named name

Returns: dict: {"returncode": int, "stdout": str, "stderr": str, "truncated": bool}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useNo
nameNo
appendNo
configNo
driverNo
bootstrapNo
node_nameNo
platformsNo
driver_optsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.0

TDQS

A5/5.0
Behavior5/5

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

Goes well beyond the generic annotations by disclosing error semantics: non-zero CLI exits do not raise, but a missing buildx plugin or timeout does, so callers must inspect returncode/stderr. It also clarifies side-effect behaviors like bootstrap timing, use-as-default, config copying, and append semantics.

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 structured with a purpose/usage paragraph, an Args list, and a Returns block. It is detailed but every sentence adds functional value; nothing is redundant with the schema, and the most important usage context is front-loaded.

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?

The tool has 9 parameters, no output schema, and sparse annotations, but the description fully compensates: it documents all parameter semantics, return shape, exception behavior, version requirements, and common invocation patterns. An agent has everything needed to call it correctly and interpret the result.

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?

With 0% schema description coverage, the description carries the full burden for all 9 parameters, and it succeeds. Every parameter gets a meaningful explanation, including examples like driver values, driver_opts conversion to --driver-opt, the buildx >= 0.17 constraint for config, and the multi-node intent of node_name.

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?

Description opens with 'Create a new BuildKit builder instance,' which is a specific verb+resource statement. It further differentiates from siblings by indicating this is the setup step before buildx_build and the counterpart to buildx_use for switching builders.

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 it is needed: when the default docker driver falls short for multi-platform builds and cache export. It also gives clear routing guidance: use=True makes it the default for later buildx_build calls, otherwise switch with buildx_use, and bootstrap=True starts the builder immediately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools