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

tc_tree

Manage TwinCAT tree items: read, create, rename, delete, import/export, and batch operations with error roll-up.

Instructions

TwinCAT System Manager tree items; paths use ^ separators (e.g. TIPC^MyPlc, TIID^Device 2 (EtherCAT)^Box 1). BATCH-FIRST: for more than one item use the matching *_batch action — N ops in ONE DTE attach, continue-on-error roll-up {count,succeeded,failed,results:[{...,ok,error?}]}, instead of an attach per call. Actions, grouped single / batch: READ identity — get / get_batch (paths:[...]); TEST existence — exists / exists_batch (paths:[...]); READ xml — get_xml (ProduceXml raw XML; summary:true for a compact identity + slot-module list); WRITE params — set_xml / set_xml_batch (items:[{path,xml}]) (ConsumeXml; compact unless returnXml:true); RENAME — rename / rename_batch (renames:[{name|path,newName}]) (keeps IO links intact); CREATE — create / create_batch (creates:[{parent,name,subType,before?,createInfo?}]); create VALIDATES the child and errors clearly on a malformed/ghost result instead of silently succeeding — adding an EtherCAT box needs a proper ESI-based createInfo (bare subType 9099 with no createInfo produces a blank-named ghost), recorded per-entry as ok:false; to ADD EtherCAT terminals/boxes from the ESI prefer the dedicated tc_ethercat tool; DELETE — delete / delete_batch (deletes:[{parent,name}], GUARDED: dryRun:true previews which children exist, confirm="ALLOW_TWINCAT_DELETE" to actually delete). Mutating *_batch verbs accept save:true to save once after the batch. No batch form: children (lists child items, incl. CPX-AP/Festo sub-modules), import (.xti under path), export (name to file), focus (Solution Explorer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xmlNo
fileNo
nameNo
pathNo
saveNo
itemsNo
pathsNo
actionYes
beforeNoinsert before this sibling
dryRunNo
confirmNo
createsNo
deletesNo
newNameNo
renamesNo
subTypeNo
summaryNo
reconnectNo
returnXmlNo
createInfoNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: batch continue-on-error roll-up result structure (count, succeeded, failed), get_xml summary mode, rename keeping IO links, create ghost detection, delete guard pattern, and save flag for mutating batches. No contradictions.

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?

The description is well-organized by action groups and front-loaded with path format and batch guidance. However, it is dense and could be slightly more concise by reducing minor repetitions (e.g., repeated mention of batch result structure). Still, every sentence adds value.

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 20 parameters, no output schema, and rich semantics, the description covers all actions, batch behavior, error handling, guardrails, and sibling context. It provides sufficient detail for an agent to correctly select and invoke the tool without missing critical behavioral aspects.

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

Parameters5/5

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

Schema coverage is only 5%, but the description elaborates on all key parameters: path format (^), arrays (items, paths, creates, deletes, renames) with required fields, and parameters like save, dryRun, confirm, summary, returnXml, before, subType, createInfo. This adds significant semantic value beyond the 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?

The description clearly states that the tool manages TwinCAT System Manager tree items with specific path separator ^. It lists numerous actions (get, children, exists, etc.) and distinguishes from sibling tools like tc_ethercat for adding EtherCAT terminals, making purpose and scope unambiguous.

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 advises using batch actions for multiple items ('BATCH-FIRST'), recommends tc_ethercat for EtherCAT hardware addition, and explains guarded delete with dryRun and confirm. It also notes create validation behavior, giving clear when-to-use and alternatives.

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