Loading ToolBench
Describe what you want to build. Kitbash tells you which parts already exist, which to adapt, and which to just write.
Two tools with moderate definition quality. Both have clear descriptions and schemas, but lack some key details for production robustness. The kitbash tool is well-named and has good parameter descriptions, while kitbash_verify follows a sensible naming pattern. However, neither tool includes error handling guidance, output schema documentation, or parameter validation constraints. Parameter descriptions are adequate but could be more prescriptive. The server correctly registers tools via the MCP SDK, but tool definitions rely on visible registration in src/tools/* files which were not provided for full inspection.
Generates a component slate with decomposition, verdicts (BORROW/KITBASH/WRITE), and ranked candidate repos for each component based on the provided idea and optional constraints (stack, target license).
Verifies a component slate by fetching GitHub metadata for all proposed repos, assesses health (recency, stars, license, fork status), ranks candidates, detects hallucinations, and generates a detailed markdown report with verdicts and fit warnings.
kitbash_verify has complex nested object schema without documented output structure. LLMs cannot plan downstream calls without knowing what the verification report contains.
No error handling guidance. Neither tool describes what to do if GitHub API fails, repos are not found, or hallucinations are detected. Agents lack recovery direction.
kitbash parameters 'stack' and 'target_license' lack enum constraints. Free-form strings invite invalid values (typos like 'typescript' vs 'TypeScript', or non-standard license names). Should use enums or pattern constraints.
kitbash_verify output schema for 'components' array shows nested structure but lacks field descriptions. The 'verdict', 'rationale', and 'candidates' fields are unexplained, LLMs cannot determine what values to expect or how to interpret results.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
kitbash tool does not document what 'ComponentCandidate' structure is. The verify tool accepts 'components' array with these objects, but the kitbash description does not explain the shape of its output or how to chain into verify.