Host-side MCP server that bridges to on-device Clojure nREPL, enabling remote evaluation of Clojure code on Android devices via Model Context Protocol
Three tools with complete input schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (clojure_eval, clojure_require, clojure_load_file), which is good. However, descriptions lack actionable detail about return formats, error conditions, and when to use each tool vs. alternatives. Parameters have types but most lack descriptions (ns parameter in clojure_require has minimal guidance; 'code' in clojure_eval lacks format/constraint info). No documented output schemas, LLMs cannot predict what fields to expect. Error handling is absent from descriptions. The 'WRITE' risk annotation on clojure_eval and clojure_require is noted but not integrated into descriptions as state-modification warnings.
Evaluate Clojure code on the running Android device via nREPL (port 6688). State persists across calls (defs, requires, etc). Returns captured stdout and the printed values after `=>`. Examples: (+ 1 2), (System/getProperty "java.vm.name").
Read a .clj file from the host filesystem and load-string it on-device. Useful when iterating on code that isn't yet packaged in the APK.
Require (or :reload) a Clojure namespace on-device, e.g. demo.ui. First load of an unseen ns triggers d8/DEX compilation and can take a while.
Output schemas not documented. LLMs cannot predict return structure (stdout, printed values, error format, etc.). Descriptions mention 'captured stdout and printed values after =>' but no formal schema.
Parameter descriptions missing or minimal. 'code' parameter in clojure_eval lacks format guidance (single form vs. multiple? Clojure syntax rules?). 'ns' in clojure_require has only 'Namespace symbol, e.g. demo.ui.', no guidance on what happens if ns doesn't exist or is already loaded.
Error handling not described. clojure_eval and clojure_require are marked WRITE risk but descriptions do not explain failure modes (nREPL connection lost, compilation error, namespace not found, timeout). No recovery guidance for LLMs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
No distinction between tool use cases. clojure_eval and clojure_require both load code on-device; descriptions do not clarify when to use eval (ad-hoc expressions) vs. require (persistent namespaces). LLMs may pick wrong tool.
clojure_load_file 'path' parameter lacks validation constraints. No guidance on absolute vs. relative paths, file extension requirements, or what happens if file doesn't exist or is not readable.