Skip to main content
Glama

lv_status

Connect to LabVIEW to report its version, install directory, and the VIs currently loaded in memory, giving AI agents a quick environment check before inspecting or running VIs.

Instructions

Connect to LabVIEW and report its version, install directory and VIs currently in memory.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lv_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the full burden. It does disclose that the tool 'connects' to LabVIEW, hinting at an external dependency, but it never says whether connecting launches a LabVIEW instance, whether it fails when LabVIEW is not running, or what latency/timeout to expect — all material for a connect-style tool.

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?

A single front-loaded sentence with the action first and the three returned artifacts listed in order. No filler, no restatement of the tool 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 zero-argument status probe with no output schema, naming the three returned fields is the key missing piece and it is present. The only remaining gap is behavioral (connection failure modes), which is minor for a read-only environment query.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter schema applies. The sentence spends its words on output content instead, which is the right allocation.

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?

The description names a concrete verb ('report') and enumerates exactly what is returned: LabVIEW version, install directory, and VIs in memory, which distinguishes it from VI-level siblings like vi_info or vi_dump. It stops short of explicitly contrasting itself with those siblings, so an agent must infer the boundary.

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?

There is no when-to-use guidance, no preconditions, and no named alternative. The agent must infer that this is the environment-level check to run before VI-level operations rather than something like vi_info.

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