Skip to main content
Glama

buildx_use

Switch the active Docker builder for buildx operations, with options to persist the choice for the current context or globally.

Instructions

Select the active builder for subsequent buildx operations.

Without default or global_default the switch applies only to the current CLI session. default persists the choice for the current Docker context; global_default persists across all Docker contexts. Use buildx_list to see available builders and their current status. To avoid switching the global default, pass a specific builder name directly via buildx_build's builder parameter instead.

args: name - Builder name to activate (from buildx_list) default - Persist as default builder for the current Docker context global_default - Persist as default builder across all Docker contexts returns: dict - {"returncode": int, "stdout": str, "stderr": str, "truncated": bool}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
defaultNo
global_defaultNo
Behavior5/5

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

The description reveals important behavioral nuances beyond the annotations: without flags the change is limited to the CLI session, 'default' persists for the current context, and 'global_default' persists across all contexts. It also warns about the impact of switching the global default and offers a non-switching alternative, giving the agent full understanding of side effects.

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 well-structured and front-loaded with the core purpose. The scoping details, usage tips, and parameter explanations each add value without redundancy. The format is clear, and the returns section neatly summarizes the output regardless of the absence of an output schema.

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?

With only three parameters, minimal annotations, and no output schema, the description covers everything an agent needs: purpose, scoping behavior, parameter meanings, return format, and explicit pointers to related tools. It is fully sufficient for correct invocation and decision-making.

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?

The schema provides no descriptions for parameters (coverage 0%), but the description's 'args' section explains each parameter in detail: 'name' is the builder to activate (from buildx_list), 'default' persists for the current context, and 'global_default' persists across all contexts. This fully compensates for the schema gap.

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 opens with 'Select the active builder for subsequent buildx operations,' a specific verb and resource that clearly distinguishes this from siblings like buildx_list (which lists) and buildx_build (which builds). The scope is explicit: it changes the active builder for subsequent operations.

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?

The description explains when to use this tool versus alternatives with concrete guidance: use buildx_list to see available builders, and avoid switching the global default by passing a specific builder name to buildx_build's builder parameter. It also clarifies the scoping semantics (session, context, global), providing clear conditions for each mode.

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