Skip to main content
Glama

build_status

Read-onlyIdempotent

Check a commissioned build in-chat: stage progress, queue position, rejection reason if the data didn't match the objective, honest ETA, report link when delivered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pipeline_idNopipeline_id from a build
track_tokenNoToken from the tracking URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pipeline_id / description
      Previous value: -"pipeline_id from a build (modify_analysis)"New value: +"pipeline_id from a build"
  2. Changed1 schema field changed
    • changedInput schema / properties / pipeline_id / description
      Previous value: -"pipeline_id from create_analysis"New value: +"pipeline_id from a build (modify_analysis)"
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value the annotations do not: the response surfaces stage progress, queue position, a rejection reason tied to objective mismatch, an 'honest' ETA, and a report link once delivered. This is valuable because there is no output schema. It still omits what happens when called with no arguments, given both parameters are optional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence with the resource front-loaded and the payload enumerated after a colon, so the reader gets the point immediately. It is efficient with no filler, though the compressed list style is close to overload for a single sentence.

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?

With two optional parameters, no output schema, and no annotations about returns, the description correctly spends its words describing what comes back. But because required is empty, an agent is left unsure what a zero-argument call does and whether pipeline_id or track_token is preferred when both are available. That is a real gap for this tool's shape.

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%: pipeline_id and track_token are both documented as 'from a build' and 'from the tracking URL'. The description adds no syntax, format, or precedence information beyond that. The baseline of 3 applies because the schema carries the parameter semantics.

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 ('Check') and a specific resource ('a commissioned build'), then enumerates exactly what the caller gets back: stage progress, queue position, rejection reason, ETA, report link. That is far beyond a restatement of the name. It does not, however, distinguish itself from the sibling 'package_status', so an agent cannot tell from the text alone which of the two to pick.

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

Usage Guidelines3/5

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

'Check a commissioned build in-chat' implies the situation (polling a build you already commissioned) but never states exclusions, prerequisites, or which sibling to use instead. There is no 'when not to use' and no mention of package_status as an alternative. Usage is inferable but not spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.