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

plc_library

Manage PLC library references and repositories in TwinCAT projects. Add, remove, or update library placeholders and resolutions via ITcPlcLibraryManager.

Instructions

PLC library references / placeholders / repositories via ITcPlcLibraryManager on the References node (TIPC^^ Project^References). referencesPath defaults to the first PLC under TIPC. READ (no side effects): list (References → name/kind library|placeholder/displayName/distributor/version), scan (ScanLibraries → installed libs name/version/distributor/displayName; pass filter to avoid the full catalogue dump), repos (Repositories → name/folder). WRITE — OFFLINE .plcproj edits, NO runtime impact (not confirm-gated): add_library (name, version?, company?), add_placeholder (name, defLib?/defVer?/defDist? — omit defLib for the name-only form), set_resolution (placeholder, lib, version?, dist?), freeze (name? — omit to freeze ALL), remove_reference (name = library or placeholder). Each accepts save:true to File.SaveAll after the edit. LANDMINE: a .plcproj library-reference edit (add/remove/repin a library or placeholder, set resolution) requires a full solution close+reopen in XAE before it takes effect; adding source files alone does not — the response surfaces this note. REPO ADMIN — GUARDED, mutates the machine-wide TwinCAT library store (no runtime change, but shared-machine state): install_library (repo, libPath, overwrite?), uninstall_library (repo, lib, version?, dist?), insert_repository (name, folder, index?), remove_repository (name), move_repository (name, index). These require confirm="ALLOW_PLC_LIBRARY_REPO". Nothing here targets the safety system (References live only under TIPC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
libNo
distNo
modeNoDTE attach mode; default active
nameNo
repoNo
saveNo
indexNo
actionYes
defLibNo
defVerNo
filterNoscan: case-insensitive substring on library name; omit for the full installed list
folderNo
companyNo
confirmNo
defDistNo
libPathNo
versionNo
overwriteNo
placeholderNo
referencesPathNoReferences node path; default = first PLC under TIPC
Behavior5/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 thoroughly discloses that READ actions are side-effect-free, WRITE actions are offline with no runtime impact and require a solution close+reopen, and REPO ADMIN mutates shared machine state and requires a confirm parameter. It also notes the safety system is not targeted.

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-structured with clear sections for READ, WRITE, LANDMINE, and REPO ADMIN. It is somewhat verbose but front-loaded with the purpose. Every sentence adds value, and the structure aids readability.

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 tool's complexity (20 parameters, multiple actions) and lack of output schema, the description is remarkably complete. It covers all action categories, side effects, prerequisites, and the critical LANDMINE note. It provides sufficient context for an agent to select and invoke the tool 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 only 15%, so the description must compensate. It explains parameters in context of actions (e.g., name, version, company for add_library; filter for scan; referencesPath default), but many parameters like lib, dist, mode, index, folder, overwrite, placeholder remain unexplained. The description provides some added meaning but is not exhaustive.

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 PLC library references, placeholders, and repositories via ITcPlcLibraryManager. It distinguishes between READ, WRITE, and REPO ADMIN actions, and the tool name and context differentiate it from sibling tools like plc_project or xae.

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 divides actions into READ (no side effects), WRITE (offline edits, no runtime impact, requires close+reopen), and REPO ADMIN (machine-wide, guarded, requires confirm). It provides clear context but does not explicitly compare to alternative tools for similar tasks.

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