Doctor-first architecture health and governance CLI for AI-built projects. MCP server for managing boilerplate scaffolding, metadata, and project updates.
boilerforge has 5 tools with basic schema definitions and descriptions. Naming follows verb_noun convention (list_, get_, search_, scaffold_, check_) which is good. However, descriptions are minimal (10-50 chars), parameter descriptions are absent or generic, and output schemas are completely undocumented. No error handling guidance. No tool annotations. The scaffold_project tool accepts a destructive write operation but lacks confirmation patterns or dry-run support. Tools are READ_ONLY or WRITE but lack explicit risk documentation in the tool definition itself. Overall: competent naming, weak descriptions, missing parameter details, no output schema docs.
Check if a scaffolded project has available updates
Get all files for a specific boilerplate
List all available boilerplates in the registry
Scaffold a boilerplate into a target directory
Search boilerplates by name, stack, or tags
No output schemas documented. Tools return data but LLMs cannot see what fields to expect. All 5 tools lack return type documentation.
Parameter descriptions are missing or generic. 'name' param in get_boilerplate has minimal description 'Boilerplate name'. No format, constraints, or examples. 'query' in search_boilerplates lacks guidance on what constitutes a valid search. 'targetPath' in scaffold_project lacks validation rules (absolute vs relative paths, permissions needed).
scaffold_project is a destructive write operation but lacks dry-run, confirmation, or rollback guidance. No description indicates this modifies the filesystem. No error handling guidance if targetPath is not writable or already contains files.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Tool descriptions are extremely brief (30-45 chars avg). Missing WHEN to use, WHAT is returned, and dependencies. E.g., scaffold_project description 'Scaffold a boilerplate into a target directory' does not explain prerequisites, success criteria, or what files are created.
No error handling guidance. If scaffold_project fails (bad boilerplate name, no write permissions, disk full), the tool offers no recovery hints. If check_project_updates fails (missing boilerforge.lock.json), no guidance on what went wrong or what to do next.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tools are marked READ_ONLY or WRITE in metadata but not in the MCP schema itself. LLMs cannot see which operations are safe to retry.
list_boilerplates accepts no pagination parameters. If registry grows to hundreds of boilerplates, returning all at once wastes tokens and risks context explosion. Missing limit, offset, and total_count fields.