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

tc_task

Manage TwinCAT RT tasks and their settings: list, create, configure cycle time and priority, bind CPU affinity, and set linked tasks for PLC projects.

Instructions

RT tasks under TIRT (+ RT-core settings under TIRS, + a PLC project's LinkedTask under TIPC). CONFIG-ONLY — no confirm token needed; runtime needs a later activate/restart; TISC (safety) untouched. Tree paths use ^ separators (e.g. TIRT^PlcTask). Actions: list (tasks under TIRT); get (path; summary:true -> identity + parsed TaskDef tags instead of full XML); create (name; withImage default true = SubType 0 / false = SubType 1 no image; before?; cycleTimeUs?/priority? applied after create via ConsumeXml; save?); set_params (path; cycleTimeUs [us, converted to 100ns ticks = us*10] / priority [0-255] / autoStart; OR xml = raw .. escape hatch [mutually exclusive with the typed fields]; returnXml?; save?). CAVEAT: the TaskDef tag names for cycle/priority/autostart are UNCONFIRMED against the AI docs — prefer the xml escape hatch and verify with get(summary) before trusting the typed fields; add_image_var (path = a with-image task's Inputs/Outputs node; varName; dataType e.g. BOOL/INT/DINT; startAddress? default -1 = append; save?); get_rt_settings (TIRS; summary:true -> parsed MaxCPUs/Affinity/per-CPU LoadLimit/BaseTime/LatencyWarning); set_rt_settings (maxCPUs / affinity [TwinCAT hex token e.g. #x0000000000000007] / cpus [{id,loadLimit?,baseTimeNs?,latencyWarningUs?}]; OR xml escape hatch; returnXml?; save?); bind_cpu (path; affinity = a name [CPU1..CPU8, MaskSingle/Dual/Quad/Hexa/Oct/All, None] OR a raw #x.. token; returnXml?; save?); get_linked_task (path? = PLC root under TIPC, default first child of TIPC); set_linked_task (path? = PLC root; linkedTask = XAE tree path of the RT task, e.g. TIRT^PlcTask; save?).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xmlNo
cpusNo
nameNo
pathNo
saveNo
actionYes
beforeNoinsert before this sibling task
maxCPUsNo
summaryNo
varNameNo
affinityNo
dataTypeNo
priorityNo
autoStartNo
returnXmlNo
withImageNo
linkedTaskNo
cycleTimeUsNo
startAddressNo
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses config-only nature, need for later activation, and that TISC is untouched. Explains summary parameter behavior, create defaults, and conversion of cycleTimeUs. Mentions unconfirmed tag names and escape hatch.

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 dense but well-structured: begins with domain, then lists actions separated by semicolons. It is appropriate for the complexity (19 params, 10 actions) but could be slightly more readable with bullet points or clearer separation.

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 high complexity, lack of output schema, and 19 parameters, the description is remarkably complete. It covers all actions, parameter behaviors, caveats, and practical usage notes, leaving little ambiguity for an AI agent.

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?

With only 5% schema description coverage, the description compensates fully, explaining parameters per action: path, summary, withImage, before, cycleTimeUs (conversion to 100ns ticks), priority range, autoStart, xml escape hatch, save, returnXml, etc. Adds meaning beyond 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 precisely states it handles RT tasks under TIRT, RT-core settings under TIRS, and a PLC project's LinkedTask under TIPC, listing specific actions. It clearly distinguishes from sibling tools focused on other subsystems.

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?

Provides clear when-to-use guidance: 'CONFIG-ONLY — no confirm token needed; runtime needs a later activate/restart; TISC (safety) untouched.' Includes caveats about unconfirmed tag names and prefers xml escape hatch. Specifies actions and their contexts.

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