hwcontract
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HWCONTRACT_ROOT | No | Absolute path to the contracts folder. Relative contract paths resolve against it. Defaults to the process's working directory. | |
| HWCONTRACT_SAFE | No | Set to '1' to instantly disable hardware-touching tools (captures) while leaving pure judge tools working. | |
| HWCONTRACT_TOKEN | No | Bearer token required when the server is exposed over HTTP (e.g., via --http). |
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 |
|---|---|
| judge_contractA | Judge observations against a contract -> pass/marginal/fail. No hardware; use for replay or when an adapter already captured. |
| capture_ws2812A | Capture the WS2812 data line via sigrok and return measured pulse-width observations (T0H/T1H/...). |
| check_ws2812A | Capture a live WS2812 signal AND judge it against a contract in one call. The one-shot an agent reaches for. |
| check_dshotB | Capture a live DShot600 ESC signal AND judge it against a contract in one call. |
| judge_serialA | Judge a captured serial log against expect/forbid patterns. No hardware; use for replay or logs another tool already captured. |
| check_serialB | Read a serial port for N seconds AND judge its log against a contract's expect/forbid patterns. |
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 6 tools
Tools are mostly distinct: check_* does live capture+judge, judge_* does offline judging, and capture_ws2812 is capture-only. However, judge_contract and judge_serial could be confused for serial logs, and capture_ws2812 vs check_ws2812 requires careful reading.
Naming mixes three verb prefixes (judge_, check_, capture_) and inconsistently references protocols (ws2812, dshot, serial) vs the generic 'contract'. The pattern is readable but not fully consistent.
Six tools are well-scoped for hardware contract testing: one generic judge, one capture, and four protocol-specific live/offline checks. This is within the ideal 3-15 range and each tool serves a distinct purpose.
The core workflow of capture and judge is covered for WS2812, serial, and DShot (via live check). Missing a DShot capture-only tool and a dedicated judge_dshot, but judge_contract fills the gap, so only minor dead ends exist.