Skip to main content
Glama

project_create

Creates a LabVIEW .lvproj under My Computer from absolute file paths and optional build specs, adding missing source files and returning project info for EXE, packed library, or source builds.

Instructions

Create a LabVIEW project (.lvproj) under My Computer holding files (absolute paths of VIs, controls, libraries, other files), optionally with build specs. LabVIEW makes the project and adds the items itself.

A build spec: {"name": "My App", "type": "exe" | "ppl" | "source", "version": "1.0.0.0", "description": "...", "output_dir": "C:/.../builds/My App" (default /builds/ ), "file_name": "MyApp.exe" (exe/ppl; default .exe / .lvlibp), plus exe (application): "startup": ["C:/.../Main.vi"] (opens when the EXE runs), "include": [always-included VIs, e.g. ones called dynamically]; ppl (packed library): "library": "C:/.../My.lvlib", "include": [...]; source (source distribution, copies the VIs and their non-vi.lib subVIs): "include": [...]}. Source files are added to the project if missing. Build it with project_build. Returns project_info of the result.

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_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
filesNo
overwriteNo
build_specsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses useful traits: LabVIEW itself creates the project and adds items, missing source files are added automatically, output_dir has a default, and the result is project_info. It omits what happens when the target path already exists and the overwrite flag is false, or whether an existing project is modified.

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?

Purpose and core behavior are front-loaded in the first sentence, then build-spec detail follows in a compact structured block. The pseudo-JSON notation is dense but each clause carries real information; there is little padding beyond the somewhat over-stuffed spec syntax.

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 filesystem-mutating create tool with no annotations and no output schema, the description covers most of what an agent needs, including the return value (project_info). The gaps are the unmentioned `overwrite` semantics and the unexplained `path` parameter, which matter because they determine whether existing data is replaced.

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%, so the description must compensate, and it does for two of four parameters: `files` is defined as absolute paths of VIs/controls/libraries, and `build_specs` is documented in detail with per-type fields and defaults. The `path` parameter is never explained (target .lvproj path?) and `overwrite` is not mentioned at all, leaving half the inputs undocumented in both places.

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: create a LabVIEW project (.lvproj) under My Computer containing the given files, optionally with build specs. The note that 'LabVIEW makes the project and adds the items itself' implicitly separates it from item-adding tools like project_add, but no sibling is named explicitly.

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 clear workflow routing: create here, then 'Build it with project_build'. It also says source files are added only 'if missing', hinting at idempotent input handling. However, it never says when to prefer this over project_add, nor when not to use it (e.g., if the project already exists and overwrite is false).

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