Skip to main content
Glama

lv_class_properties

Retrieve LabVIEW VI Server class properties by name or keyword, filtered by query, so you can reference them in property nodes for VI creation and editing.

Instructions

Properties of a VI Server class as LabVIEW lists them (All Supported Properties), filtered by query (words in the name or long name, e.g. "visible", "plot color"). Use "name" in a property node's "properties" in vi_create / vi_edit. class_name is a class like "Boolean", "Digital", "WaveformChart", "Control", "VI", "Application"; a node linked to a front-panel object has that object's class (vi_dump / vi_text show the control type; its parent classes also apply).

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": {
      "class_name": "<class_name>"
    },
    "name": "lv_class_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
class_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It usefully discloses inheritance behavior ('a node linked to a front-panel object has that object's class ... its parent classes also apply') and that results reflect LabVIEW's own listing, but it does not state whether the operation is read-only or describe the returned structure.

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 core statement is front-loaded and every clause carries information (filter semantics, downstream use, class derivation). The heavy parenthetical nesting makes it dense and slightly hard to scan, but no sentence is wasted.

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 lookup with no output schema and no annotations, the description covers how to call it, how to derive class_name, and how the output is consumed. The one gap is that the shape of the returned property list (e.g. names vs long names) is only hinted at.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates: query is defined as matching words in the name or long name with concrete examples ('visible', 'plot color'), and class_name is defined with example values and a method to obtain it (vi_dump / vi_text show the control type). This adds real meaning beyond the bare schema types.

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 specific resource and verb-equivalent ('Properties of a VI Server class ... filtered by query') and states the listing scope ('All Supported Properties'). It implicitly separates itself from lv_functions by being about class properties, but never explicitly contrasts with a sibling, keeping it below a 5.

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?

It gives clear downstream guidance: 'Use "name" in a property node's "properties" in vi_create / vi_edit', which tells the agent exactly what the result feeds into, and it shows how to filter via query. There is no explicit when-not-to-use or alternative-tool routing, so it stops short of a 5.

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