MCP server for controlling and querying SmallTV-Ultra devices via local HTTP API
SmallTV Ultra provides 5 tools with complete input schemas and descriptions, but quality is uneven. Tool names follow verb_noun convention (smalltv-get, smalltv-read, smalltv-write, smalltv-upload-*), which is good. Descriptions are present but generic (10-80 chars, below the 50-200 char baseline for LLM optimization). Parameters have types and descriptions, but lack constraints (enums, ranges, patterns). Error handling returns structured JSON with type/message fields, which is solid. However, no output schemas are documented, and descriptions do not explain WHEN to use each tool or dependencies between them. The firmware upload tool correctly implements a confirmation pattern for irreversible operations, but other tools lack guidance on retryability and error recovery.
Retrieve device information from SmallTV endpoint /v.json
Read data from a SmallTV device endpoint via GET request
Upload image files (JPG, JPEG, GIF) to SmallTV device
Upload firmware file to SmallTV device (requires explicit confirmation)
Write data to a SmallTV device endpoint via HTTP request (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS)
No output schemas documented. LLMs cannot predict response structure or plan downstream tool calls. Each tool returns structured JSON (device_ip, status_code, body, etc.) but this is not formally declared.
Descriptions are too short (10-80 chars vs. 50-200 char baseline). They state WHAT the tool does but not WHEN to use it or how it differs from similar tools. E.g., smalltv-read vs smalltv-write distinction is unclear from descriptions alone.
Parameters lack constraints. device_ip is optional (falls back to SMALLTV_IP env var) but this dependency is not documented in the parameter description. path parameter requires '/' prefix but no regex pattern or enum is declared. method parameter accepts arbitrary strings instead of an enum of valid HTTP methods.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
Error messages are structured but lack recovery guidance. E.g., 'upstream_unreachable' error does not suggest retry strategy or alternative actions. 'invalid_response' does not explain what format was expected.
smalltv-read tool includes validation logic to reject write endpoints (/set, /wifisave, /delete, /update, /doUpload) but this constraint is not documented in the path parameter description. LLMs cannot infer this restriction.