Skip to main content
Glama

vi_diff

Compare two versions of a LabVIEW VI to list semantic changes: nodes added or removed, constants with new values, renamed controls, moved objects, and wire changes. Also shows what the newest backup edit changed.

Instructions

What changed between two versions of a VI, as a list of semantic changes: nodes added and removed, constants with new values, controls renamed or retyped, objects moved into another structure or frame, and wires added and removed. path_a is the old version, path_b the new one. Without path_b it compares the newest vi_edit backup of path_a (.lvmcp-backup/) with path_a, so after vi_edit it shows exactly what the edit did. Objects are matched by their LabVIEW UID, which survives edits. Neither file is 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_a": "<path_a>"
    },
    "name": "vi_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
path_aYes
path_bNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it declares that neither file is changed, explains the matching mechanism (LabVIEW UID survives edits), and documents the fallback comparison against .lvmcp-backup/. Gaps remain around edge cases — what happens when no backup exists or a path is invalid — but the core behavioral profile is disclosed.

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-loaded with what it returns, then parameter semantics, then default behavior, then matching and non-mutation. Every sentence adds information and there is no filler.

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 two-parameter read tool with no annotations and no output schema, the description covers return content, parameter roles, default behavior, matching semantics, and side effects. Only failure modes and the exact shape of the returned list are left implicit.

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 schema titles are only 'Path A'/'Path B', so the description must supply all meaning — and it does, defining path_a as the old version, path_b as the new, and specifying that omitting path_b triggers backup comparison. It does not state expected path format (absolute vs relative, .vi extension), leaving a small gap.

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 — diff of two VI versions — and immediately enumerates the change categories it reports (nodes added/removed, constant values, renamed/retyped controls, moves between structures, wires). This is clearly distinct from siblings like vi_dump or vi_info, which the agent can differentiate without opening a 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?

Gives concrete usage context: it is the tool to call after vi_edit to verify what an edit did, via the implicit backup comparison. It does not explicitly name an alternative or state when not to use it, but the post-edit verification scenario is clear enough to route an agent.

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