Pugi

Get the status of a build

job_status

Idempotent

Use this when the person asks how a Pugi build or change is going, or for a fresh preview link. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Preview links expire after 15 minutes; call again for a fresh link.

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": "job_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The job_id build_site, build_app or edit returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / job_id / description

Previous value: -"The job_id build_site or edit returned."New value: +"The job_id build_site, build_app or edit returned."

AddedOct 26, 2026
RemovedOct 25, 2026
AddedOct 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare safety hints, so the description carries the burden and does it well: it discloses terminal states to poll for, the 15-minute preview link expiry, and the host-dependent behavior (automatic card tracking vs. manual polling). That is real operational context not recoverable from annotations or schema.

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?

Front-loaded with the user-facing trigger, then branches cleanly by host, then closes with the expiry caveat. Every sentence adds a distinct rule; nothing is repeated.

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?

For a one-parameter, no-output-schema polling tool, the description covers invocation, polling loop termination, host differences and link lifetime. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the single job_id parameter is already documented in the schema, including which tools return it. The description reinforces this but adds no format, validation or edge-case detail beyond the schema, so baseline 3 applies.

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 names a specific verb and resource ('job_status' reports how a build or change is going) and adds a second purpose, fetching a fresh preview link. It ties job_id back to build_site, build_app and edit, so the agent can place it among siblings without opening the schema.

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?

Gives explicit when-to-use guidance split by host: no polling in MCP Apps/ChatGPT widget hosts where a build card exists, and repeated polling with job_id in Claude Code/API hosts until the job is finished, stopped or failed. It also names the trigger condition for a second call (expired preview link).

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

All Pugi tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?