Skip to main content
Glama

vi_info

Retrieve metadata for a LabVIEW VI file, including type, version, state, unsaved changes, callers/callees, and broken-VI error details from its path.

Instructions

Metadata for one VI: type, description, LabVIEW version it was saved in, broken/idle state, unsaved changes, subVIs it calls (callees) and callers loaded in memory. A broken VI also gets "errors": LabVIEW's Error List (why it is broken), each {"error", "details", "count"}.

path: absolute path to a .vi/.vit/.ctl/.vim file.

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": "vi_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 behavioral burden and does disclose useful traits: it is a metadata read, it reports broken/idle state and unsaved changes, and it attaches an 'errors' array with {error, details, count} for broken VIs. It does not state whether LabVIEW must be running, whether files are opened or locked, or whether the call has any side effects, which matters most given zero annotation coverage.

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?

Front-loads the resource and its returned fields, then adds the conditional 'errors' detail, then the parameter semantics. Three compact statements with no filler or redundancy.

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?

No output schema exists, so the description must describe returns, and it does list the fields including the shape of each error entry. Gaps remain around the structure of callees/callers entries and any failure behavior, but the essentials for calling it correctly are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter has no description in the schema, so the description must compensate. It does: 'absolute path to a .vi/.vit/.ctl/.vim file' clarifies both path form and accepted file extensions, which the schema does not convey.

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 ('Metadata for one VI') and enumerates the returned fields: type, description, saved LabVIEW version, broken/idle state, unsaved changes, callees and callers. That is enough to distinguish it from vi_run or vi_edit, though it does not explicitly contrast with close siblings like vi_hierarchy or vi_dump that also surface structural information.

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

Usage Guidelines2/5

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

The description never says when to use this tool versus alternatives; there are no preconditions, exclusions, or named siblings. An agent must infer usage purely from the field list, which is suggestive but not guidance.

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