MCP server for the Argus autonomous research and engineering runtime, providing project management, messaging, status monitoring, and artifact access
Argus MCP server has 7 tools with basic naming and descriptions, but significant gaps in schema completeness and parameter documentation. All tools have descriptions (10-80 chars), but most are terse and lack actionable context. Input schemas are present but sparse: most parameters lack detailed descriptions explaining constraints, formats, or dependencies. No output schemas documented. Error handling guidance is absent. Tool names follow verb_noun convention (argus_*) but lack clarity about what distinguishes similar operations (e.g., argus_status vs argus_doctor). No tool annotations (readOnlyHint, destructiveHint) despite clear risk classifications. Parameter descriptions are minimal, 'project identifier' repeats across 5 tools without explaining how to obtain a project_id or what happens on invalid input.
List existing allowlisted artifacts selected by Argus.
Run non-mutating Argus runtime and backend diagnostics.
Send one operator turn through the Argus Manager front door.
Create an idle Argus project bound to an existing work directory.
List Argus projects, optionally filtered by exact work directory.
Read bounded persisted status for one Argus project.
Stop an Argus project, draining gracefully unless force is explicit.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., project_id from argus_project_create). Violates pattern:tool and pattern:response-shaper.
Parameter descriptions are generic and lack actionable constraints. 'project identifier' appears 5 times without explaining format, how to obtain it, or what happens on invalid input. Violates pattern:tool-description and review:param-validation-rules.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications (READ_ONLY, WRITE, REVERSIBLE). LLMs cannot infer safety properties. Violates pattern:command-tool.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Tool descriptions are terse (35-55 chars) and lack WHEN/WHY context. 'Send one operator turn through the Argus Manager front door' is cryptic, does not explain when to use argus_message vs argus_status. Violates pattern:tool-description.
No error handling guidance. Tools do not document what errors are retryable, user-fixable, or fatal. No recovery hints (e.g., 'If project not found, call argus_project_list'). Violates pattern:recovery-guide.