Skip to main content
Glama

vi_hierarchy

Builds a breadth-first subVI call tree from a LabVIEW VI, with configurable depth and optional vi.lib, user.lib, and instr.lib inclusion.

Instructions

SubVI call tree starting at a VI (breadth-first, up to max_depth levels). Callees inside the LabVIEW install (vi.lib, user.lib, instr.lib) are hidden unless include_vilib=true.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
max_depthNo
include_vilibNo

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 must carry the behavioral load, and it does disclose two meaningful traits: traversal is breadth-first and callees inside vi.lib/user.lib/instr.lib are suppressed by default. It does not state the result shape (nested tree vs list), behavior on a missing/invalid VI, or whether the call is purely read-only, leaving notable gaps 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?

Two tight sentences with the core behavior front-loaded and the exception clause second. Nearly every word earns its place; only a minor cost is that the parenthetical directory list is slightly verbose relative to its value.

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 three-parameter read tool with no output schema and no annotations, the description covers traversal order, depth limiting, and the default filtering rule, which is the essential calling context. It falls short only on output format and the semantics of the required `path` argument.

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%, so the description has to compensate. It successfully explains max_depth (limits levels traversed) and include_vilib (reveals install-library callees, with the directories named), but says nothing about what `path` expects (absolute path, relative, project-relative) or depth-bound edge cases. Two of three parameters gain meaning; the required one does not.

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?

Names a specific artifact and operation: a SubVI call tree starting at a given VI, with breadth-first traversal. That is far more informative than a generic 'get hierarchy', though it never distinguishes itself from related siblings such as vi_dump or vi_info, which an agent could plausibly confuse for a structural listing.

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 by the traversal semantics; there is no statement of when this tool is preferred over vi_dump, vi_info, or vi_text, and no prerequisites (e.g. the VI must be loaded/on disk) are given. The default-hiding rule hints at a 'use include_vilib when you need library internals' workflow, but that is left for the agent to infer.

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