Delta PLC Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| environment.probeA | Inventory local installations without opening an IDE or contacting a PLC. |
| target.resolveC | Resolve exact model and compatible adapter; ambiguous selection stays explicit. |
| capabilities.listD | Read implementation and qualification separately; this grants no authority. |
| workspace.createC | Create isolated file workspace. This is not native project.create; optional baseline is copied from configured read roots. |
| workspace.statusC | Verify context and original baseline hashes and read workspace identity. |
| workspace.importB | Copy a hash-locked input from configured read roots; destination is workspace-relative and must not exist. |
| adapter.invokeB | Invoke an explicitly registered typed capability. No arbitrary shell/eval; backend qualification and authority gates remain in force. |
| evidence.readB | Read durable operation evidence, including incomplete intents after restart. |
| workflow.startA | Create a durable W1..W7 workflow; does not execute or grant authority. |
| workflow.runC | Execute explicit allowed steps once; dependent queued work stops the chain for evidence review. |
| workflow.statusC | Resume visibility after disconnect without retrying side effects. |
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 11 tools
Tools map to distinct lifecycle phases (probe, capabilities, target, workspace, adapter, evidence, workflow) and descriptions carefully delimit boundaries, e.g. workspace.create vs workspace.import and workflow.start vs workflow.run. Minor potential confusion remains between the create/import and start/run pairs, but the descriptions resolve it.
All 11 tools follow a strict namespace.verb pattern (environment.probe, workspace.create, workflow.run, adapter.invoke, etc.). The convention is applied uniformly with no style deviations.
11 tools is well within the ideal range and each earns its place, covering the full lifecycle from environment discovery through workflow execution. No redundant or filler tools are present.
The surface covers discovery, target resolution, workspace lifecycle, capability invocation, evidence reading, and workflow orchestration. Minor gaps exist: no workspace teardown/delete, no workflow cancel/abort, and no evidence listing, but these are workaroundable.