Zero-install context discipline for Claude. Generates CONTEXT_MANIFEST.md and dependency graphs to reduce token consumption by 5-27x. Provides structural code analysis, manifest generation, and context-aware file discovery.
Single tool 'context_mapper' has a reasonable description (145 chars, within 10-1024 range) but critical schema deficiencies. Input schema is present with two parameters ('path' and 'dry_run'), both with descriptions. However, NO output schema is documented anywhere in the code or README. The tool description states it 'Generates CONTEXT_MANIFEST.md and a lightweight dependency graph' but does not specify what fields/structure the agent receives back. Without documented output schema, LLMs cannot plan downstream operations or extract relevant data. The tool performs a read-only analysis (no state mutation), which is appropriate, but lacks error handling guidance, recovery paths, and output structure documentation required for agent integration.
Manifest Generator + Graph Builder. Generates CONTEXT_MANIFEST.md and a lightweight dependency graph. Scans project files, extracts imports, builds dependency graph, and generates structured manifest with file metadata, language detection, and blast radius analysis.
No output schema documented. Tool description states it generates manifest and dependency graph but does not specify return fields, structure, or format. LLMs cannot infer what data is available for downstream use.
Tool name 'context_mapper' is vague. Does not start with action verb (get_, create_, analyze_, generate_). 'context_mapper' could mean map contexts, generate context maps, or analyze context. Rename to 'generate_context_manifest' or 'analyze_project_context' for clarity.
No error handling or recovery guidance. If path is invalid, unreadable, or too large, the tool provides no actionable error message. Description does not explain prerequisites (path must exist, be readable, etc.) or what to do if analysis fails.
Parameter 'path' lacks format/constraint documentation. Description says 'Project root path to analyze' but does not specify: must be absolute or relative? Must exist? Max depth? Size limits? LLMs will guess and pass invalid paths.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Tool description does not explain WHEN to use it or what problem it solves. 'Manifest Generator + Graph Builder' is technical jargon. Rewrite as: 'Analyzes a project directory to generate a structured manifest of files, dependencies, and language distribution. Use this to understand project structure before refactoring or onboarding.'