PLC Agentics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port used for the optional HTTP mode, e.g. HTTP_PORT=3000 node src/cli.js serve. This mode exposes the same tools as a REST API for assistants without MCP support. | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_brandsA | Returns all PLC brands and IDEs supported by PLC Agentics, with their common programming languages. |
| get_brand_configA | Returns brand-specific configuration for a PLC: memory areas, data types, naming conventions, ST syntax quirks, supported IEC 61131-3 languages, and project structure. Always call this before generating code for a specific brand. |
| get_code_templateA | Returns a ready-to-adapt IEC 61131-3 code template for a common automation pattern. Use this as the structural starting point, then fill in the user-specific logic. |
| list_templatesA | Lists all available code templates with a short description of each. |
| get_iec61131_referenceA | Returns IEC 61131-3 language reference: keywords, standard function blocks, data types, and syntax rules for the requested language. Use this to ensure generated code is spec-compliant. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose within the PLC knowledge lookup domain: listing brands vs. getting brand config, listing templates vs. retrieving a template, and fetching IEC 61131-3 reference. The descriptions explicitly clarify when to use each, so an agent should not confuse them.
All names follow a consistent snake_case verb_noun pattern: list_brands, list_templates, get_brand_config, get_code_template, get_iec61131_reference. The convention is predictable throughout the set.
Five tools is well-scoped for a reference/lookup server focused on PLC brands, templates, and language references. Each tool earns its place and there is no redundant or trivial tool.
The surface covers the core lookup lifecycle: discover brands, retrieve brand configuration, list and retrieve code templates, and access IEC 61131-3 syntax rules. Minor gaps remain, such as a dedicated validation tool or template search by pattern, but agents can work around these using existing tools.