Dockerized Poke PC MCP worker with tmux terminal control, Poke tunnel, and adaptive webhook notifications.
Server has 7 tools with basic schemas and descriptions. Most tools have input schemas with type constraints (minLength, format, min/max), but descriptions are generic and lack actionable context. terminal_run_command and terminal_capture_output have reasonable parameter constraints. However, descriptions do not explain WHEN to use each tool, what prerequisites exist, or how to chain them. Error handling is minimal, no recovery guidance or actionable error messages. Output schemas are not documented. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Naming is verb-noun compliant but generic (terminal_*, filesystem_*). Parameter descriptions exist but are terse (avg ~40 chars vs baseline 72 chars).
Read a file from disk. Paths under ~/.config are blocked to protect credentials and local secrets.
Capture recent output lines from a command window
Create or ensure a tmux session exists
Get status for a previously started command
Kill a tmux session
List tmux sessions known by the server
Run a shell command inside a dedicated tmux window within a session
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. terminal_kill_session is DESTRUCTIVE but unmarked; terminal_run_command is WRITE but unmarked. LLMs cannot infer safety properties without explicit hints.
Descriptions lack actionable context. 'List tmux sessions known by the server' does not explain WHEN to call this (before run_command? to verify cleanup?). No dependency hints or prerequisites. Baseline: 194 chars; actual avg ~45 chars.
Output schemas not documented. Tools return {content, structuredContent} but LLMs do not know what fields structuredContent contains or how to extract data for chaining. E.g., terminal_run_command returns commandId but this is not documented in output schema.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2025-06-18+ | v2 |
No error recovery guidance. If terminal_run_command fails (e.g., session not found), the response does not suggest calling terminal_create_session first. Errors are silent failures without actionable next steps.
filesystem_read_file blocks ~/.config but does not document this restriction in the description. LLMs will attempt to read from blocked paths and receive silent failures. Constraint must be explicit in description.