Skip to main content
Glama

Control Plane

by io.cpln

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. Read on an interval, never in a tight loop. Recommended reading before first use: get_cpln_skill("image") — the runbook for this tool family (read once per session).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesOrganization 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.
buildIdYesThe `buildId` build_image returned. Never construct one.
logOffsetNoOpaque 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.
includeLogNoOmit 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.
maxLogLinesNoCap on log lines returned (default 80); the newest are kept.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary.
summaryYesOne-line summary of the result.
nextStepsNoRecommended follow-up actions for this task, in order.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description doesn't need to repeat that. It adds valuable context: statuses enumeration (queued/building/pushed/failed), automatic log behavior on failure, and the polling guidance. It doesn't describe output format, but that's covered by the output schema. Slight gap: no mention of potential errors or rate limits beyond 'never in a tight loop', but the guidance suffices for behavioral transparency.

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 a single, dense paragraph of about 80 words. It front-loads the core purpose, then explains statuses, log behavior, polling cadence, and a prerequisite reading reference. Every sentence adds value; there is no fluff or repetition of schema details. Highly efficient.

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 that the tool has an output schema (not shown but existence is noted) and complete schema descriptions for all 5 parameters, the description covers the key operational context: status lifecycle, log retrieval conditions, polling guidance, and a pointer to the runbook. For a read-only, idempotent tool, this is comprehensive. No missing elements like error handling or auth are necessary given the existing annotations.

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

Parameters3/5

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

Schema description coverage is 100%; every parameter has a detailed description in the schema. The tool description adds minimal extra insight: it explains the logOffset resume cursor concept ('Echo back nextLogOffset... Only NEW output') and emphasizes includeLog's default behavior, which complements the schema. However, the description doesn't significantly add beyond the schema—the schema already covers semantics. Thus baseline 3 is appropriate.

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 explicitly states: 'Read a build started by build_image: its status, its progress events, and its log.' It names the source tool (build_image) and clearly differentiates from sibling tools like get_workload_logs and get_workload_events by focusing on image build status and log. The verb 'Read' plus the resource 'build started by build_image' is specific and unambiguous.

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 provides explicit usage guidance: 'Read on an interval, never in a tight loop' and 'Recommended reading before first use: get_cpln_skill("image") — the runbook for this tool family (read once per session).' It also explains when includeLog is needed and when it's not, contrasting with default behavior. No explicit exclusions of alternatives are needed because the purpose is so narrowly scoped.

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

All Control Plane toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Every tool targets a distinct resource/action pair (e.g., get_resource vs get_resource_schema, list_deployments vs list_workload_replicas) and descriptions clearly differentiate purposes. No two tools appear to do the same thing.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern (create_gvc, update_workload, list_resources, query_metrics) with consistent verbs. The few imperative verbs (browse, build, mount) still maintain the same verb-first structure.

Tool Count1/5

With 55 tools, this server far exceeds the typical well-scoped 3-15 tool range. While each tool appears purposeful, the sheer number creates selection overhead and falls into the extreme 50+ category on the rubric.

Completeness4/5

The surface covers nearly the full Control Plane lifecycle: CRUD for GVC, workload, identity, policy, volumeset, and domain, plus observability, templates, image builds, and Terraform. Minor gaps include referenced but missing configure_workload_* tools and no secret creation/deletion (by design).

Resources