Multi-instance Claude Code manager with a bundled web UI for orchestrating multiple Claude Code agents from one place.
Critical gaps across all dimensions. Tool descriptions are present but generic (avg ~50 chars, well below 194-char baseline). No visible input schemas in source code, cannot verify parameter types, constraints, or descriptions. Tool names follow verb_noun convention (positive), but lack specificity (e.g., 'invoke_agent' is vague about what happens). No evidence of output schema documentation. Error handling absent, no recovery guidance, categorization, or actionable messages. Security concerns: notify_user and invoke_agent are write operations with no visible permission gates or audit trails. Composition issues: artifact tools (write/edit/delete/read/list/find/move) are well-factored, but agent tools lack clear dependencies and chaining support. STDIO transport caps protocol readiness at 50, further limiting production viability.
Convert between epoch values and readable local time
Delete an artifact
Delete a circle artifact
Edit an existing artifact
Edit an existing circle artifact
Find content in an artifact
Find content in a circle artifact
Get detailed information about a specific agent
Get the last message from a specific agent
No input schemas visible in source code. Cannot verify parameter types, constraints, enums, or descriptions. All 22 tools score 0 on schema dimension.
Descriptions are generic and under 50 characters (well below 194-char baseline). Examples: 'Send a notification to the user' (32 chars), 'Edit an existing artifact' (25 chars). LLMs cannot distinguish when to use invoke_agent vs get_agent_details or write_artifact vs write_circle_artifact.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
Navigate a large JSON payload without burning the context window
Invoke another agent with a task or prompt
List available agents in the system
List artifacts
List circle artifacts
List the MCP servers you can assign to agents you design. Use a returned id in an agent's mcpServerIds.
Move an artifact
Send a notification to the user
Read an artifact
Read a circle artifact
Search the workspace for documents and fragments
Write a new artifact
Write a new circle artifact
Destructive operations (delete_artifact, delete_circle_artifact) lack confirmation/dry-run support and no visible permission gates. No audit trail or error recovery guidance.
invoke_agent and notify_user are write operations with no visible permission checks, scope declarations, or audit logging. Agents can invoke other agents or notify users without authorization verification.
No output schema documentation visible. LLMs cannot plan downstream tool calls or extract required fields (e.g., does list_agents return agent_id for use in invoke_agent?).