Skip to main content
Glama

lv_functions

Search LabVIEW palette functions by name, with query words matching in any order, to find exact function names for vi_create and terminal lookup.

Instructions

Search LabVIEW's palette functions by name (words match in any order), e.g. "array", "string length", "file". Use the exact name as "function" in vi_create, and call function_terminals(name) to learn its terminal names.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.40.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the matching rule (words match in any order) but is silent on case sensitivity, substring vs. exact matching, result count limits, and whether results are names only or include metadata.

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?

Three tight sentences: purpose first, matching semantics second, follow-up workflow last. No filler and nothing buried.

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 one-parameter search with no output schema and no annotations, the definition covers purpose, matching behavior, and the follow-up calls. The main residual gap is the shape of the result set (names only vs. richer entries), which an agent would want before chaining into vi_create.

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 single parameter is only titled "Query", so the description must compensate. It does: the query is a function name search where words match in any order, illustrated with examples, which is meaningful guidance beyond the bare schema.

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 ("Search LabVIEW's palette functions by name") plus the matching semantics (words match in any order) and three concrete example queries, so an agent knows exactly what this retrieves without opening the 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 clear downstream guidance: use the returned exact name as "function" in vi_create, and call function_terminals(name) to learn terminal names. It does not state explicit exclusions or contrast with other search-like siblings, but the workflow context is unambiguous.

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