MCP (Model Context Protocol) compliant server for M5StamPLC industrial controller, providing digital I/O, relay control, sensor reading, and system management capabilities
This server has 13 tools with basic schemas and descriptions, but exhibits significant quality gaps. Tool naming is solid (all start with action verbs like 'read', 'write', 'get', 'set'), and all tools have non-empty descriptions. However, parameter descriptions are inconsistent, many lack depth beyond the bare parameter name. Output schemas are NOT documented anywhere in the source, which is a critical omission. Error handling is absent from the visible code. The server's design is hardware-focused (PLC I/O control) rather than agent-optimized, and parameter constraints (ranges, enums) are missing. Schema completeness is moderate, all visible tools have type definitions, but lack of output documentation and validation rules significantly reduces quality. Average per-tool score: 52/100.
Log a message to the device console
Get the state of all inputs and relays
Get the current IO socket output current reading
Get the current power voltage reading
Get all sensor data readings at once (temperature, voltage, current)
Get information about the system
Get the current temperature reading
Output schemas completely undocumented. No tool documents what fields or structure it returns. LLMs cannot plan downstream tool calls or extract needed data.
Parameter descriptions are minimal (10-30 chars). Example: 'readInput' param 'inputNumber' described as 'The digital input number to read', no guidance on valid range (0-X?), what happens on invalid input, or format. LLMs cannot self-correct on bad input.
No parameter constraints (enums, min/max ranges). Tools like 'tone' accept frequency and duration as bare integers with no bounds. LLMs could pass frequency=0 or duration=999999, causing errors or device hang.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | D | 53 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 39 | - | v1 |
Get the current time from the RTC
Read the state of a digital input
Read the state of a relay
Set the RTC time
Play a tone with specified frequency and duration
Set the state of a relay
No error handling or recovery guidance in visible code. No tool documents what happens on failure (invalid input number, relay offline, time out of range). LLMs cannot know whether to retry, ask the user, or move on.
Tool descriptions lack WHEN/WHY guidance. 'Get information about the system' does not explain when to call it instead of getIOState, what 'system info' includes, or what structure is returned.
Destructive/write operations (writeRelay, setTime, tone) lack confirmation or dry-run support. An agent could accidentally relay a physical device or set wrong time without safeguards.