Skip to main content
Glama
Edge-JB
by Edge-JB

tc_module

List, create, and configure TcCOM module instances. Use XML for parameters and symbols, enable DataArea symbols, and assign to task execution contexts. Configuration-time only, no runtime activation.

Instructions

TcCOM module objects under TIRC^TcCOM Objects (paths use ^ separators). CONFIG-TIME ONLY — no INIT/PREOP/SAFEOP/OP transitions (not an Automation Interface feature); nothing here activates config, downloads, or touches the runtime/safety system. Actions: list (read-only) — enumerate module instances via ITcModuleManager3, returns {count,modules:[{moduleTypeName,moduleInstanceName,classId,oid,objectId,parentOid}]} (oids are DECIMAL; XAE shows hex). create (name, by="classid"|"name", id, before?) — CreateChild under TcCOM Objects: by=classid -> subType 0, id = module GUID/ClassID e.g. {8f5fdcff-...}; by=name -> subType 1, id = registered module type name e.g. "NewModule"; a malformed/ghost child is cleaned up and reported as an error. get_xml (path) — ProduceXml of the instance (Parameters / DataAreas / Symbols, with current CreateSymbol/CreateSymbols flags). set_xml (path, xml, returnXml?) — ConsumeXml escape hatch for parameters not exposed as typed properties. enable_symbols (path, parameters?, dataAreas?, returnXml?) — convenience toggle: sets CreateSymbol=true on Parameter nodes and/or CreateSymbols=true on DataArea AreaNo nodes via ProduceXml/ConsumeXml. CAVEAT: the XPath/attribute names are from a how-to summary, NOT verified against a literal ProduceXml dump — call get_xml on a real module first and fall back to set_xml if the toggle reports changed:false. To wire module DataArea symbols to PLC/IO/other-module variables (symbols must already exist via enable_symbols), use tc_link link/unlink. set_context (path, taskObjectId, contextId?) — assign the instance to a task's execution context; taskObjectId/contextId are DECIMAL oids (XAE shows hex). GUARDED: changes the activated mapping/runtime context, requires confirm="ALLOW_TWINCAT_MODULE_CONTEXT" and defaults to no-op.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byNo
idNo
xmlNo
nameNo
pathNo
actionYes
beforeNoinsert before this sibling under TcCOM Objects
confirmNo
contextIdNo
dataAreasNo
returnXmlNo
parametersNo
taskObjectIdNodecimal ObjectId of the target task (XAE shows it in hex)
Behavior5/5

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

With no annotations, the description fully carries the burden of disclosure. It details that list is read-only, create may clean up malformed children, set_xml is an escape hatch, set_context is guarded and defaults to no-op, and that XPath/attribute names are unverified from a how-to summary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy (approx. 350 words) and includes redundant explanations (e.g., 'CONFIG-TIME ONLY' repeated, details on list output). It is well-organized with actions clearly separated, but could be more succinct without losing clarity.

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?

Given the complexity of 13 parameters and multiple actions with no output schema, the description comprehensively covers each action's behavior, parameter usage, error handling, and prerequisites (e.g., call get_xml first). It also mentions return values for list and provides caveats about verification, ensuring the agent has sufficient context.

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 low (15%), but the description adds significant meaning for nearly all parameters: it explains each action, the path structure, create parameters (name, by, id, before), xml and returnXml for set_xml, boolean parameters for enable_symbols, and taskObjectId/contextId with decimal notation for set_context. Slight deduction for not fully describing path or confirm in all contexts.

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 manages 'TcCOM module objects under TIRC^TcCOM Objects', specifies it is 'CONFIG-TIME ONLY' and not for transitions, and lists specific actions with their purposes. It distinguishes from sibling tool 'tc_link' which handles wiring of symbols.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (config-time only) and when not to (no runtime transitions). Provides alternatives: 'To wire module DataArea symbols ... use tc_link link/unlink.' Also advises calling get_xml before set_xml for parameter toggle verification.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Edge-JB/TwinCAT-XAE-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server