Skip to main content
Glama

project_add

Add files and build specifications to an existing LabVIEW project, skipping duplicates and rejecting reused build spec names. Close the project in LabVIEW first if it has unsaved changes.

Instructions

Add files and/or new build specs (same format as project_create) to an existing project. Files already in the project are skipped; a build spec name already in use is refused. LabVIEW opens, saves and closes the project, so close it in the LabVIEW IDE first if it has unsaved changes there.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
filesNo
build_specsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that existing files are skipped, that a duplicate build-spec name is refused, and that LabVIEW opens, saves, and closes the project as a side effect, plus the precondition of unsaved IDE changes. It stops short of describing errors or results when both optional arguments are omitted.

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?

Three front-loaded sentences with no filler; the skip/refuse rules and the IDE precondition each appear once and are easy to scan. The last sentence is slightly dense but still readable.

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 three-parameter mutation tool with no annotations and no output schema, the description should also cover the 'path' meaning and what a caller gets back (created counts, skipped/refused items). The safety preconditions are present, but these gaps leave the call under-specified.

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 only partly does: it defines build_specs' format by reference to project_create and gives skip semantics for files. The required 'path' argument is never explained (project file versus project directory), and no path-format or relative-path guidance is given for files.

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 ('Add files and/or new build specs ... to an existing project') and explicitly scopes against the sibling operation by pointing at project_create for the spec format. An agent can distinguish this from project_create and project_build without opening either 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?

Implies when to use it (project already exists) versus when to use project_create, and names the refusal/skip conditions that determine whether a call is a no-op. It does not state what to do about a brand-new project or a project whose specs must be replaced rather than added, so it falls short of fully explicit 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.