Skip to main content
Glama

function_terminals

Retrieve exact LabVIEW function terminal names to wire nodes correctly in vi_create, avoiding mismatches between Context Help labels and scripting engine identifiers.

Instructions

Exact terminal names of one palette function, verified against LabVIEW's scripting engine (Context Help labels sometimes differ, e.g. "Variant" vs "variant"). Wire them in vi_create as ".". "help_labels" lists the Context Help text; inputs usually carry a default in parentheses there. Growable nodes are wired as element[1..N] instead.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that names are engine-verified rather than Context-Help labels, and that a 'help_labels' field is returned with default values in parentheses. It does not state whether the call is read-only, what happens for an unknown function name, or error behavior — gaps that matter for a lookup tool with no annotation coverage.

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?

Front-loaded with the purpose, then caveats and wiring format; each sentence carries information. Dense but readable, with only mild redundancy between the Context Help note and the help_labels note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, the description does explain the shape of returned terminal names and the help_labels field. It is incomplete on the 'size' parameter and on failure behavior, which leaves an agent guessing for the nullable argument.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It implies 'name' is a palette function name, but adds no format example, and the 'size' parameter is never addressed — the mention of growable nodes as element[1..N] hints at sizing without ever tying it to the parameter.

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?

States a specific resource and qualifier: 'Exact terminal names of one palette function,' verified against the scripting engine. An agent can tell this is a name-resolution lookup, distinct from listing functions (lv_functions) or creating nodes (vi_create), though no sibling is named explicitly.

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 clear downstream context — wire results into vi_create as '<node>.<terminal>' and use element[1..N] for growable nodes — plus a caveat about Context Help labels differing. It stops short of stating exclusions or when to prefer another tool, but the usage context is unambiguous.

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