Claude's missing better half — a companion tool for Claude Code. A desktop and mobile application providing a headless backend for remote access with MCP server capabilities.
Claudette exposes only 1 tool (open_devtools) with a minimal description (79 chars). The tool lacks a visible input schema in the provided source code, no JSON Schema definition, parameter types, or constraints are evident. The description states what the tool does but provides no guidance on when to use it, prerequisites, or expected behavior. No parameter documentation is visible. The tool appears to be a simple GUI action (opening dev tools) rather than an agent-oriented capability. Without schema visibility and proper parameter documentation, this cannot score higher.
Opens the webview inspector on the calling window. Triggered from the Help → Open dev tools menu item.
No input schema visible for open_devtools. Cannot verify parameter types, constraints, or structure.
Tool description (79 chars) lacks context for LLM selection. Does not explain WHEN to call this tool, what prerequisites exist, or what the return value is. Descriptions should be 10 - 1024 chars with clear WHAT/WHEN/WHY guidance.
No parameter documentation visible. If open_devtools accepts parameters (e.g., window_id, dev_tools_mode), they must have descriptions explaining their purpose and valid values.
Tool is GUI-centric (opens webview inspector), not agent-oriented. MCP tools should expose capabilities that agents can compose into multi-step workflows. A GUI action that requires user interaction is not suitable for autonomous agent use.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | <=2025-11-25 | v2 |
No output schema documented. LLMs need to know what open_devtools returns (success/failure, status code, error message) to plan downstream actions.