Skip to main content
Glama

build_status

Reports an FPGA build job's progress and, once finished, fetches its outputs and returns the build report. Optionally waits up to 50 seconds for completion before responding.

Instructions

Report a build job's progress; when it has finished, fetch the outputs and return the report.

wait_seconds: wait up to this long (max 50) for the job to finish before answering.

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": {
      "job_id": "<job_id>"
    },
    "name": "build_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 full burden. It usefully discloses that on completion the tool fetches outputs and returns a report, and that wait_seconds is capped at 50 — a constraint absent from the schema. However, it says nothing about what happens when the job hasn't finished (does it return partial progress, a status field, an error?), nor about failing/unknown job IDs, nor about the report's shape despite there being no output schema.

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?

Two short sentences, front-loading the core purpose before the parameter note. Nothing is padded, though the wait_seconds explanation sits slightly awkwardly as a standalone line rather than integrated into a single coherent flow.

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 asynchronous status tool with no annotations and no output schema, the description covers the interaction model (block up to N seconds, then answer) but leaves the return contract vague — 'return the report' does not tell an agent what fields to expect for an in-progress versus finished job. Adequate to call correctly, incomplete for interpreting results.

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 description coverage is 0%, so the description must compensate. It does so for wait_seconds, explaining the blocking semantics ('wait up to this long... before answering') and the undocumented max of 50. job_id is left to inference from the tool's purpose and name, which is a minor but real 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?

States a specific verb and resource ('Report a build job's progress') and adds the completion behavior (fetch outputs, return the report), which clearly separates it from the sibling 'build' that starts a job. It does not explicitly contrast itself with siblings like 'report' or 'install_status', but the purpose is unambiguous on its own.

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?

Usage is only implied: the wait_seconds parameter signals this is a polling tool, so an agent can infer 'call repeatedly until finished.' There is no explicit statement of when to use this versus checking status another way, no guidance on how often to poll, and no named alternative.

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