Skip to main content
Glama
Sign In
node-opcua-modeler-mcp-server

node-opcua-modeler-mcp-server

Official
by node-opcua
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_type_details

Retrieve detailed information about an OPC UA type, including its components, properties, methods, interfaces, and optional members, to understand its structure before creating instances or subtypes.

Instructions

Get detailed information about a specific type: its components, properties, methods, interfaces, and optional members. Use this to understand a type's structure before creating instances or subtypes.

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": {
      "alias": "<alias>",
      "browseName": "<browseName>"
    },
    "name": "get_type_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYesCompanion spec alias where the type is defined (e.g. "machinery")
browseNameYesThe type browse name (e.g. "MachineryItemIdentificationType")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly indicates a read operation without side effects but does not elaborate on return format, pagination, or any potential restrictions. This is adequate but not rich.

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?

The description is two sentences long with no extraneous text. It efficiently communicates the tool's purpose and usage context.

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 tool with 2 simple parameters and no output schema, the description sufficiently covers what the tool does and when to use it. It lacks details on return format but is otherwise complete.

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 coverage is 100%, with both parameters (alias, browseName) described in the schema. The description does not add additional meaning beyond what the schema provides, such as constraints or examples. Baseline 3 is appropriate.

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 clearly states the tool retrieves detailed information about a specific type, listing components, properties, methods, interfaces, and optional members. This distinguishes it from sibling tools like list_types (which likely lists types) and search_types (which searches), making the purpose specific and actionable.

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 description explicitly advises using the tool to understand a type's structure before creating instances or subtypes. While it does not list when not to use it, the use case is clear and contextually relevant.

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

Deploy Server

Other Tools