MCP server for Siemens TIA Portal automation and project management
TIA-MCP exhibits significant definition quality gaps. Tool names follow verb_noun convention (Connect, Disconnect, GetState, etc.), which is positive. However, parameter descriptions are minimal or absent across most tools. 10 of 14 tools have empty input schemas ({}), providing zero guidance on what they accept or return. The 4 tools with parameters (OpenProject, GetSoftwareInfo, GetDeviceInfo, GetDeviceItemInfo, GetBlockInfo, GetTypeInfo) have basic type info but lack depth. Descriptions are present but generic (e.g., 'Get information about a device'). No output schemas are documented, forcing LLMs to guess response structure. Error handling is present in code (McpException with error codes) but not surfaced in tool definitions. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications in metadata. Tool composition is reasonable (single responsibility), but lack of schema documentation breaks tool chaining.
Close the currently open TIA-Portal local project/session
Connect to TIA-Portal
Disconnect from TIA-Portal
Get information about a block
Get information about a device
Get information about a device item
Get all devices in the current TIA-Portal project
10 of 14 tools have empty input schemas ({}). This prevents LLMs from understanding what parameters are accepted or required.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., device IDs for chaining). ResponseConnect, ResponseState, ResponseGetProjects classes exist in code but are not exposed in tool definitions.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | <=2025-11-25 | v2 |
Get open local project/session
Get the project structure/tree on the current TIA-Portal project
Get information about PLC/HMI software
Get the state of the TIA-Portal MCP server
Get information about a user-defined type
Open a TIA-Portal local project/session
Save the current TIA-Portal local project/session
Tool annotations missing. Risk metadata (READ_ONLY, WRITE) exists in tool list but not in tool definitions as readOnlyHint/destructiveHint. LLMs cannot infer safety/idempotency from names alone.
Parameter descriptions are minimal. 'path: defines the path where to the project/session' lacks format guidance (absolute vs relative? Windows vs Linux?). No enum constraints, regex patterns, or length limits documented.
No pagination support visible. GetDevices, GetProjectTree, GetProject likely return lists but no limit/offset/page parameters or total_count in response. Large results risk context window exhaustion.