Covas annotation workspace MCP server that provides tools for managing image annotation sessions, rendering the annotation widget, and persisting session state in Codex projects.
Covas MCP server has 4 tools with complete input schemas and descriptions, but quality is uneven. Tool names follow verb_noun convention (render_, save_, get_, submit_) which is good. However, descriptions are domain-specific and assume deep familiarity with Covas internals (CanvagentSessionManifest, pageStateById, etc.). Parameter descriptions lack actionable constraints, no enums, ranges, or format guidance. Output schemas are not documented. Error handling is absent. The bootstrap.manifest parameter in render_covas_workspace_widget is particularly opaque: it references an undocumented type (CanvagentSessionManifest) with no guidance on structure or required fields. No tool has error recovery guidance. Composition is reasonable (4 distinct operations), but the interface is tightly coupled to internal data structures rather than user-facing concepts.
Reads the current Covas session manifest from the user project directory. Returns imagesById, imageOrder, activeImageId, and pageStateById. Use this to list available versions before calling render_covas_workspace_widget.
Opens the Covas annotation workspace as a native widget in the Codex sidebar. Pass projectDir to persist session data in the user project. Pass bootstrap.manifest to restore a previous session state.
Persists the current Covas annotation session manifest to the user project directory. Called automatically by the widget on state changes, or manually to checkpoint before navigation.
Submits the annotated image from the Covas workspace back to Codex.
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (sessionId, manifest structure, etc.). Violates pattern:tool requirement that tools document return types.
Parameter descriptions reference undocumented internal types (CanvagentSessionManifest, SubmitPayload, pageStateById). LLMs cannot infer structure or required fields. Descriptions must be self-contained or link to schema definitions.
No error handling or recovery guidance. Tools lack descriptions of failure modes, retryability, or next steps. E.g., what happens if projectDir does not exist? What if manifest is malformed?
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2025-06-18+ | v2 |
Parameters lack constraints. sessionId, pageId, activeImageId are free-form strings with no format, length, or pattern guidance. preferredDisplayMode has an enum (good), but others do not.
Tool descriptions assume domain expertise. 'CanvagentSessionManifest, imagesById, imageOrder, activeImageId, pageStateById' is a field list, not a user-facing description. Rewrite to explain WHAT the tool does and WHEN to call it.