Skip to main content
Glama

project_build

Builds LabVIEW project build specifications with NI Application Builder, returns generated files such as the EXE, and reports broken VIs so you can fix and rebuild.

Instructions

Build a project's build specification with NI's Application Builder (empty build_spec = build all of the target's specs). Returns the generated files (the .exe first for an application). A broken VI fails the build with LabVIEW's list of broken VIs and reasons; fix them (vi_snapshot / vi_edit) and build again. The built EXE needs the LabVIEW Run-Time Engine of this LabVIEW version on the machine that runs it.

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": {
      "path": "<path>"
    },
    "name": "project_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
targetNoMy Computer
build_specNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return payload ordering (.exe first for an application), the failure mode (broken VI aborts the build with LabVIEW's list of broken VIs and reasons), and a runtime dependency (target machine needs the matching LabVIEW Run-Time Engine). It omits whether the call is long-running/blocking and whether it overwrites prior build output.

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?

Four sentences, front-loaded with the core action and the build_spec special case before the failure and runtime notes. Every sentence adds information; the Run-Time Engine note is the only one bordering on tangential context.

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?

There is no output schema, and the description compensates by describing returned files and their ordering, plus the broken-VI failure output. For a three-parameter build tool this is nearly complete, with the remaining gap being the meaning of path and target and expected call duration.

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 0% across three parameters, so the description must compensate. It clarifies build_spec semantics (empty = build all of the target's specs), but says nothing about what path refers to (the project file) or what target means beyond the schema default 'My Computer'. Partial compensation only.

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 specific verb and resource: builds a project's build specification using NI's Application Builder. The scope note about empty build_spec and the generated .exe output makes it clearly distinguishable from siblings like vi_run, lv_mass_compile, or vi_test without opening a schema.

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?

Gives concrete usage context: empty build_spec means build all of the target's specs, and when a build fails due to broken VIs, fix them with vi_snapshot / vi_edit and build again. It names remediation siblings but does not explicitly state when to choose this over other build-adjacent tools, so it stops short of full when/when-not guidance.

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