An agentic harness with chat TUI, headless run, and ops capabilities. Includes MCP adapter, LLM routing, and chat daemon services.
Tartarus Harness exposes 15 tools with basic schemas and descriptions, but falls short of production quality. All tools have descriptions (10-80 chars, mostly under 100), but many are terse and lack actionable context. Input schemas are present but minimal: most parameters lack type constraints, enums, or validation guidance. No output schemas documented. Parameter descriptions are sparse or missing entirely. Tools exhibit naming inconsistencies (memory vs memoryId, id vs taskId) that force LLMs to guess field mappings. Error handling is absent, no recovery guidance, no categorization. Security concerns: agent_onboard_mcp accepts arbitrary URLs without validation; no audit trail visible. Composition issues: memory_remember has two alternative fields (content/memory) without clear precedence; plan_update_item has three alternative fields (id/taskId, assignedTo/assigned_to) creating ambiguity. No pagination on search tools despite unbounded result sets. Overall, definitions are skeletal, suitable for internal coordination but not production agent tooling.
Create a new agent.
Delete an agent.
Grant a tool to an agent.
List all agents in the system.
Onboard an MCP server for an agent.
Reconfigure an agent.
Revoke a tool from an agent.
Update an existing agent.
Ambiguous parameter naming: memory_remember accepts both 'content' and 'memory'; plan_update_item accepts 'id'/'taskId' and 'assignedTo'/'assigned_to'. LLMs cannot determine which field to use, forcing guessing and failed calls.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., agent IDs after agent_create). Breaks tool composition.
Search tools (memory_search, session_search) lack pagination parameters (limit, offset, cursor). Unbounded result sets risk context window exhaustion and token waste.
No error handling guidance. Tools provide no recovery hints, error categorization, or actionable messages. LLMs cannot self-correct on failures.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Remove one persisted Tartarus memory by id.
Persist a concise memory for later recall across Tartarus sessions.
Search persisted Tartarus memories by content, category, or tag.
Replace the shared server-side coordination plan with a list of plan items.
Return the shared coordination plan, dependency summary, and ready/blocked items.
Update status, assignee, or content for one shared coordination plan item.
Search persisted and currently loaded Tartarus session transcripts.
agent_onboard_mcp accepts arbitrary 'mcpUrl' without validation or security constraints. No rate limiting, URL sanitization, or permission checks visible. High injection risk.