Skip to main content
Glama

buildx_history_inspect

Read-only

Inspect a build record by ref to retrieve full details on duration, materials, attestations, and errors, enabling debugging of failed or slow builds.

Instructions

Inspect a single build record by ref, parsed from --format json.

Returns the full record for one build — duration, materials, attestations, error (if any) — for debugging a failed or slow build found via buildx_history_list. Requires buildx >= v0.13. Raises RuntimeError if the CLI call fails.

args: ref - Build record ref. Pass the ref field from buildx_history_list directly — it reports a qualified "//", but history inspect only accepts the bare id, so this reduces it to the id and (unless builder is given) targets the builder named in the ref. Empty/omitted inspects the most recent build; the ^N syntax (e.g. "^0" = latest) is also valid. builder - Builder instance the build ran on (defaults to the one in ref, else active) returns: dict - The parsed build record (or {"raw": } if the output isn't a JSON object)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNo
builderNo
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description goes well beyond that by disclosing version requirement, RuntimeError on CLI failure, ref normalization from qualified to bare id, default builder selection, and fallback to {'raw': stdout} for non-JSON output. This is rich behavioral context that annotations do not provide.

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 with a clear main statement, a use-case sentence, and a dedicated args section. Every sentence adds value, covering behavior, constraints, and parameters without redundancy. It is appropriately detailed for the tool's complexity.

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 no output schema, the description explains the return format (full record or {'raw': stdout}) and covers errors, version requirements, parameter semantics, and defaults. It also ties to buildx_history_list. The description is complete and leaves no major gaps for an agent to invoke it 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?

Despite 0% schema description coverage, the description fully documents both parameters. For 'ref', it explains the qualified form, reduction to bare id, empty/omitted behavior, and ^N syntax. For 'builder', it clarifies the default logic. This far exceeds the bare schema and is essential for correct usage.

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 tool inspects a single build record by ref, using 'Inspect a single build record by ref' and contextualizes it for debugging failed or slow builds. It differentiates itself from sibling buildx_history_list (list vs inspect) and specifies the data source ('found via buildx_history_list').

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

Usage Guidelines4/5

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

The description gives explicit context: use for debugging failed or slow builds, and requires buildx >= v0.13. It also references obtaining ref from buildx_history_list, which implies workflow. However, it does not explicitly discuss when not to use this tool or compare it to other siblings, so it stops short of full 5.

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