CNB Remote MCP

Overview Schema Source Related Servers Discussions Admin

Get build status

build_status

Read-onlyIdempotent

Retrieves the overall and per-pipeline status of a specific CNB build using its SN so you can check whether the build or any pipeline failed.

Instructions

Get the overall status and per-pipeline status of one build (by SN, e.g. cnb-xxx). SN values come from build_list / build_trigger / npc_dispatch.

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

Input Schema

Name	Required	Description	Default
`sn`	Yes	Build SN
`repo`	Yes	Repository path, e.g. "owner/repo" or "group/subgroup/repo"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that the response includes both overall and per-pipeline status, which is useful given no output schema, but says nothing about failure behavior for an unknown SN or the open-world call's latency/availability.

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 tight sentences with the core action and the identifying key front-loaded, followed by the provenance hint. No redundant restatement of the title or annotations.

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

Completeness4/5

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

For a two-parameter read-only tool with full schema coverage and safety annotations, the description covers purpose, input provenance, and the shape of the return value. Minor gaps remain around what constitutes each pipeline status and error handling, but nothing essential to invoking it is missing.

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 coverage is 100%, so the baseline is 3, but the description goes beyond "Build SN" by stating the expected SN shape (cnb-xxx) and its provenance from build_list / build_trigger / npc_dispatch. It adds nothing for the repo parameter, which the schema already documents.

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?

States a concrete verb+resource ("Get the overall status and per-pipeline status of one build") and narrows scope to a single build identified by SN, which separates it from build_list and other siblings. The example SN format "cnb-xxx" further pins down what it operates on.

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?

Explicitly tells the agent where SN values originate (build_list / build_trigger / npc_dispatch), which is the key precondition for calling it. It does not state a when-not case or name an alternative for related needs such as logs, so it falls short of full routing guidance.

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