Skip to main content
Glama

project_info

Reads a LabVIEW .lvproj file to return targets, project items with paths, and build specs—without opening or modifying the project.

Instructions

Contents of a LabVIEW project (.lvproj): targets, items (with project path like "/My Computer/Main.vi" and file path) and build specifications (type, startup and always-included VIs, output folder and primary output, version). Reads the file; nothing is opened or changed.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key trait that the operation is a pure file read that opens and changes nothing. It does not cover failure behavior (missing or malformed .lvproj), whether LabVIEW must be installed, or whether large projects are truncated, so meaningful gaps remain for a no-annotation tool.

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 returned contents are front-loaded in one dense sentence, followed by a short statement of side-effect freedom. The parenthetical lists are informative rather than filler, though the single sentence is long enough that the read-only guarantee could have been stated earlier.

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, so the description must describe the return shape, and it does so adequately by naming the top-level sections and the notable fields within build specifications. Combined with the read-only guarantee, an agent has enough to call it correctly; only error and path-format behavior are missing.

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 the single parameter is documented only as 'Path'. The description compensates partially by tying the input to a LabVIEW project file (.lvproj), which tells the agent what kind of path to supply. It does not clarify whether the path is absolute or relative, or whether the project must be closed.

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 resource ('Contents of a LabVIEW project (.lvproj)') and enumerates what is returned: targets, items with project and file paths, and build specifications with type, startup VIs, output folder and version. That is far more specific than the bare name, and it implicitly separates it from VI-level siblings like vi_info by scoping to a project file.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the tool for inspecting project structure, and 'Reads the file; nothing is opened or changed' hints it works without opening the project in LabVIEW. There is no explicit statement of when to prefer this over vi_info or project_build, and no exclusions or preconditions (e.g., file must exist, must be a valid .lvproj).

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