Skip to main content
Glama

OPC UA Modeler

by io.github.node-opcua

Generate NodeSet2 XML

opcua_model_generate
Read-onlyIdempotent

Generate OPC UA NodeSet2.xml and Symbols.CSV from a YAML model. Requires an API key (set OPCUA_MODELER_API_KEY env var). Returns base64-encoded artifacts if the model is valid, or diagnostics if validation fails. Optionally set include_docs=true to also generate markdown documentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yamlYesThe full YAML model source to generate from
include_docsNoSet to true to include markdown documentation (slower)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the operation read-only and idempotent; the description adds that an API key is required, outputs are base64-encoded, invalid models return diagnostics, and include_docs incurs a slower execution. This goes beyond the structured annotations without contradicting them.

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 sentences with the core purpose front-loaded. Each sentence covers a distinct aspect: action, prerequisites/returns, and optional behavior, with no wasted words.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with rich annotations and no output schema, the description is sufficient: it names required auth, return format, error behavior, and the optional flag. An agent has enough information to invoke it correctly.

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 100%, so the schema already documents both parameters fully. The description mentions 'from a YAML model' and optionally re-states include_docs=true, but it does not add new meaning beyond what the input schema provides.

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?

The description states a specific verb and resource: it generates OPC UA NodeSet2.xml and Symbols.CSV from a YAML model. This clearly distinguishes it from sibling tools like validate or reverse by naming both the input and the output artifacts.

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?

The phrase 'from a YAML model' and the output artifacts establish a clear use case: producing NodeSet2 artifacts from a YAML source. It does not explicitly name alternatives or provide when-not-to-use conditions, but the context is clear and it includes an important prerequisite (API key).

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

All OPC UA Modeler toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource or operation: unit lookup, reusable-block lookup, DSL reference, type details, namespaces, type listing/search, and the four model operations are all clearly separated. Even the two search-like tools (find_reusable_block and search_types) have different intents and return different kinds of results, so an agent should not misselect.

Naming Consistency3/5

Most utility tools follow a verb_first_snake_case pattern (find_*, get_*, list_*, search_*, resolve_*), but the four workflow tools use an opcua_model_* prefix (create, generate, reverse, validate). This is a blend of two systematic conventions rather than chaotic naming, but it is not fully uniform.

Tool Count5/5

Twelve tools is well within the ideal range for this domain, and each tool covers a distinct aspect of the modeling workflow from discovery and dependency resolution to validation and artifact generation. No tool feels redundant, and the count is appropriate for the stated purpose.

Completeness5/5

The tool surface covers the full lifecycle: discovering namespaces/types/units/reusable blocks, resolving dependencies, authoring YAML, validating it, generating artifacts, and reverse-engineering existing NodeSet files. There are no obvious dead ends or essential missing operations for the OPC UA modeling workflow.

Resources