Loading ToolBench
MCP server that gives Claude Code stack-aware codebase exploration tools for NestJS, Next.js, and plain TypeScript projects.
Karta provides 5 well-named, read-only codebase exploration tools with clear descriptions (avg 156 chars) and complete input schemas. All tools follow verb_noun naming (read_, get_, find_, get_) and include actionable descriptions with use-case guidance. However, output schemas are not documented in the visible code, parameter descriptions lack format/constraint details, and error handling is minimal. No tool annotations (readOnlyHint, etc.) despite all being read-only. Composition is strong, tools chain logically (read_project_structure → get_tech_stack → get_architecture_graph). Missing: pagination guidance, result limits, and recovery hints in error cases.
Search a project for files related to a keyword. Looks at filenames, exported class/function names, and variable names. Returns up to 10 ranked matches with a 3-line snippet — use this to LOCATE code before reading whole files.
Build a stack-aware architecture graph of the project. Picks the right strategy automatically: NestJS @Module decorator graph (with circular-import risks), Next.js route map (App or Pages Router), or a file import graph for plain Node/TS projects. Call this BEFORE making cross-file changes so you understand module relationships.
Summarize the public surface of a folder. Loads every .ts file in the given folderPath (recursive) and reports its exported functions, classes, interfaces, and types plus a one-line inferred summary. Use this to understand a module without reading every file.
Inspect package.json and report the detected framework (NestJS, Next.js, both, or plain Node), key dependencies with versions, and warnings about notably outdated frameworks. Call this BEFORE choosing how to read an unfamiliar codebase.
Return a nested JSON tree of folders and files for a target project. Use this FIRST when you need a quick mental map of an unfamiliar codebase before reading any files. Skips node_modules/.git/dist/.next/build/coverage/.turbo. Max depth 6.
Output schemas not documented. LLMs cannot plan downstream calls or extract fields without knowing return structure. All 5 tools lack documented return types.
No tool annotations despite all tools being read-only. Missing readOnlyHint would help agents understand safety and retry semantics.
Parameter descriptions lack format/constraint details. 'projectPath' and 'keyword' lack guidance on valid formats, length limits, or character restrictions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
No pagination or result-limit guidance. find_relevant_files returns 'up to 10' but no offset/limit params; get_module_summary loads all .ts files recursively without bounds.
Error handling lacks recovery guidance. No indication of what to do if projectPath is invalid, keyword yields no results, or circular imports are detected.