Skip to main content
Glama

get_build

Retrieve the build status and logs for a specific service release, waiting up to 60 seconds. Use after deploying with wait=false to check completion and diagnose failures.

Instructions

Bir sürümün derleme durumu ve logu (en fazla 60 sn bekler). deploy_service wait=false ile çağrıldıysa kullan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serviceId": "<serviceId>",
      "releaseId": "<releaseId>"
    },
    "name": "get_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
releaseIdYes
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden, and it does disclose the important blocking trait: it waits at most 60 seconds. It does not say what is returned if the build is still running when that deadline hits, whether the log is truncated, or whether repeated calls are safe to poll.

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?

Two compact sentences with zero filler, leading with what the tool returns and its timing constraint before the routing hint. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no annotations and no output schema, the definition covers the essentials of purpose, timing, and trigger. It leaves meaningful gaps around timeout return behavior, log size limits, and the meaning of releaseId relative to serviceId.

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

Parameters2/5

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

Schema coverage is only 50%: serviceId is documented in the schema, but releaseId is undocumented there and the description only alludes to "a release" in passing. No format, source of the id, or distinction from serviceId is offered, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: it returns the build status and log of a release ("Bir sürümün derleme durumu ve logu"). That is clearly distinct from siblings like get_service_logs or get_service, though it never names an alternative by name to sharpen the boundary.

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?

It gives an explicit usage condition: call it when deploy_service was invoked with wait=false. That is a genuine when-to-use rule rather than an implied one. It stops short of full guidance, since it does not say what to do when the build is already complete or whether the tool should be polled repeatedly.

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