Skip to main content
Glama

lv_mass_compile

Recompile and save every VI under a LabVIEW folder after upgrades or code moves; returns problems for VIs that fail to load, are broken, or cannot be saved.

Instructions

Mass compile every VI under a folder in this LabVIEW version (recompiles and saves them; use after upgrading LabVIEW or moving code). "problems" lists the log lines about VIs that failed to load, were broken or could not be saved; an empty list means all compiled cleanly.

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": {
      "directory": "<directory>"
    },
    "name": "lv_mass_compile"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does disclose the key trait: this is a mutating operation that saves files in place, not a read-only check. It also explains the return payload ('problems' lists log lines for VIs that failed to load, were broken, or could not be saved, with an empty list meaning success), which is the most operationally important behavior. It omits whether compilation is recursive into subfolders, how long it may run, or requirements like LabVIEW being closed.

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 sentences, both earning their place: the operation and its trigger are front-loaded, and the return-value semantics are compactly delivered in a parenthetical. No filler or restatement of the name.

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 one-parameter tool with no annotations and no output schema, the description covers the operation, its motivation, and the shape of the return value, which is the main risk area (silent partial failure). It is only short of complete because success/failure granularity and recursion behavior beyond the word 'under' are left implicit.

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% and there is a single required 'directory' parameter, so the description must compensate. It does establish that the value is a folder path and that VIs 'under' it are treated, hinting at recursion, but gives no format, absolute-vs-relative path, or project-relative guidance.

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 gives a specific verb and scope: 'Mass compile every VI under a folder in this LabVIEW version', and clarifies what compiling entails ('recompiles and saves them'). An agent can distinguish this from vi_run, project_build and the other siblings without opening any 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?

It names the triggering situations explicitly ('use after upgrading LabVIEW or moving code'), which gives clear when-to-use context. It does not state when not to use it or point to an alternative tool for partial/selective compiles, so it stops short of a 5.

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