Control Plane

Get an Image Build Status and Log

get_image_build

Read-onlyIdempotent

Read a build started by build_image: its status, its progress events, and its log. Statuses are queued and building (still running), pushed (done), and failed. The log comes back automatically when the build failed, since that is where the cause is; pass includeLog to see it otherwise. Pass waitSeconds to wait on the server until the build finishes.

Input Schema

TableJSON Schema

Name	Required	Description
`org`	No	Organization slug.
`buildId`	Yes	The `buildId` build_image returned. Never construct one.
`logOffset`	No	Opaque resume cursor. Echo back `nextLogOffset` from the previous response so each read returns only NEW output. Never compute, guess or add to this number. Omit to read from the start.
`includeLog`	No	Omit for the default: the build log is returned only when the build FAILED, where it is the diagnosis. Set true to also read it while building or after success — it is large, so only when the user asked to see it.
`maxLogLines`	No	Cap on log lines returned (default 80); the newest are kept.
`waitSeconds`	No	Seconds to wait on the server until the build is pushed or failed, 0 to 45. The call returns as soon as it is, or with the latest state when the time runs out. Use this instead of calling again and again.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedSep 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / buildId / maxLength
```
Removed value: -128
```
removedInput schema / properties / buildId / minLength
```
Removed value: -1
```
removedInput schema / properties / buildId / pattern
```
Removed value: -"^[A-Za-z0-9._-]+$"
```

changedInput schema / properties / org / description

Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."

removedInput schema / properties / org / maxLength
```
Removed value: -63
```
removedInput schema / properties / org / minLength
```
Removed value: -1
```

removedInput schema / properties / org / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

addedInput schema / properties / waitSeconds

Added value: +{
+  "description": "Seconds to wait on the server until the build is pushed or failed, 0 to 45. The call returns as soon as it is, or with the latest state when the time runs out. Use this instead of calling again and again.",
+  "maximum": 45,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / required

Previous value: -[
-  "org",
-  "buildId"
-]New value: +[
+  "buildId"
+]

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / data / description

Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."

addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / nextSteps / description

Removed value: -"Recommended follow-up actions for this task, in order."

removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```

AddedAug 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description goes further by disclosing non-obvious behavior: the log auto-returns only on failure, that waiting happens server-side up to a limit, and that the log is large. These are behavioral traits an agent could not infer from annotations or schema alone.

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?

Three dense sentences with the core purpose front-loaded and no filler. Every clause conveys either returned content, status semantics, or a parameter's intended use.

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?

An output schema exists, so return shape need not be restated, and the description still covers status vocabulary, log-return conditions, and the polling-vs-wait decision. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description nonetheless adds semantic intent for the load-bearing parameters, explaining WHY to pass includeLog and waitSeconds rather than just what they are. It does not discuss logOffset or maxLogLines, but the schema carries those.

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?

States a specific verb (read) and resource (a build started by build_image), and enumerates what is returned: status, progress events, and log. It clearly complements rather than duplicates the sibling build_image, and enumerates the status values, so an agent knows exactly what it is selecting.

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 routes usage: the log comes back automatically on failure, includeLog is only for reading it while building or after success, and waitSeconds is prescribed 'instead of calling again and again.' This gives concrete when/when-not guidance tied to alternatives.

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

All Control Plane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.