Skip to main content
Glama

vi_test

Run a LabVIEW VI across multiple input cases, compare outputs to expected values, and return pass/fail summaries with mismatch details.

Instructions

Test a VI against many input sets at once: run it once per case and compare the outputs. cases: [{"name": "zero gain", "inputs": {"Gain": 0, "x": 5}, "expect": {"y": 0}}, {"inputs": {"x": [1, 2]}, "expect": {"sum": 3.0, "mean": 1.5}, "tol": 1e-6}, ...] Numbers match within tol (relative to the expected value, at least absolute tol), arrays and clusters (lists) element by element, strings and booleans exactly. Returns "summary" ("9/10 cases passed") and per case "passed" with the mismatches (expected vs got) or the error. Same rules as vi_run: it executes code; only test VIs the user asked to run.

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>",
      "cases": "<cases>"
    },
    "name": "vi_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
tolNo
pathYes
casesYes
timeout_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, and the description carries the burden well: it discloses that the tool executes code, that it repeats execution once per case, how comparison is performed (numeric tolerance, element-wise for arrays/clusters, exact for strings/booleans), and what the result contains (summary, per-case 'passed', mismatches or error). It omits timeout/abort behavior and any rate or workspace-scoping caveats.

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?

The purpose leads, then the format example, then the comparison rules, then the safety note — a sensible order. The multi-line example earns its space by demonstrating the case object shape, though the description runs long relative to the simple contract it describes.

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?

With no annotations and no output schema, the description supplies both the side-effect profile and the return shape, which is what an agent most needs. The remaining gap is the undocumented 'timeout_s' and 'path' semantics and undefined behavior when a case times out or the VI fails to load.

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 description coverage is 0% across four parameters. The description compensates strongly for 'cases' (full inline example showing name/inputs/expect and a per-case 'tol' override) and for 'tol' (relative-to-expected semantics with an absolute floor), but says nothing about 'path' or 'timeout_s', leaving half the parameters documented nowhere.

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 specific verb and resource: 'Test a VI against many input sets at once: run it once per case and compare the outputs.' This clearly separates it from the single-run sibling vi_run, and the return claim (summary plus per-case pass/fail) confirms the contract.

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 a clear safety/authorization condition ('only test VIs the user asked to run') and frames the batch-per-case use case that distinguishes it from a single execution. It stops short of explicitly naming vi_run as the alternative for one-off runs, relying on the reader to infer it.

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