a starter pack for anything - Artifact-backed repository with MCP tools for editing, diffing, committing, and deploying
mcpu exposes 9 tools with minimal descriptions and incomplete schemas. Tool names use repo.* and grant.* prefixes but lack action verbs (e.g., 'repo.status' instead of 'get_repo_status'). Most descriptions are generic placeholders ('repo.status for this Artifact-backed repo') under 50 chars, providing no context for LLM selection. Input schemas are present but sparse: most parameters lack descriptions (e.g., 'grant' param has description, but 'path', 'contents', 'message' lack detail on format/constraints). No output schemas documented. Error handling is minimal, tools throw generic errors without recovery guidance. The grant.create tool has the most complete schema with 4 parameters and descriptions, but others are skeletal. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels (WRITE, IRREVERSIBLE). Overall, definitions are functional but far below production quality.
grant.create for this Artifact-backed repo
repo.commit for this Artifact-backed repo
repo.deploy for this Artifact-backed repo
repo.diff for this Artifact-backed repo
repo.history for this Artifact-backed repo
repo.ls for this Artifact-backed repo
repo.read for this Artifact-backed repo
Tool names lack action verbs. 'repo.status' should be 'get_repo_status'; 'repo.write' should be 'update_file' or 'write_file'. LLMs infer intent from verb-noun patterns.
Descriptions are generic placeholders (<50 chars). 'repo.status for this Artifact-backed repo' does not explain WHAT it returns, WHEN to call it, or WHY. LLMs cannot select tools without context.
Input parameters lack descriptions. 'path' in repo.read has no description of format/constraints; 'contents' in repo.write lacks guidance on encoding/size limits; 'message' in repo.commit is undescribed.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | 2026-07-28+ | v2 |
repo.status for this Artifact-backed repo
repo.write for this Artifact-backed repo
No output schemas documented. Tools return JSON but LLMs cannot plan downstream calls without knowing field names/types. E.g., repo.commit returns 'artifact' object but structure is not declared.
No tool annotations despite clear risk levels. repo.deploy is IRREVERSIBLE but lacks destructiveHint; repo.read is READ_ONLY but lacks readOnlyHint. Agents cannot reason about safety.