TypeScript/JavaScript AST analysis server providing tools for code inspection, complexity analysis, call graphs, and structural diffing
Solid foundation with 9 well-named, verb-prefixed tools (analyze_, call_, get_, code_, dead_, diff_, find_). All tools have descriptions (avg 120 chars, within baseline 34-392). Input schemas present for all tools with typed parameters. However, output schemas are NOT documented, LLMs cannot predict return structure. Error handling uses safeTool wrapper but lacks recovery guidance (e.g., 'try search_users first'). No tool annotations (readOnlyHint). Parameter descriptions are minimal (e.g., 'Absolute path to the TS/JS file' repeated 8 times). Missing enum constraints on direction/scope parameters despite having valid values. No pagination support despite tools that could return large result sets (analyze_package, dead_code, call_graph).
Provides a high-level summary of a TypeScript/JavaScript file's own symbols: classes, interfaces, types, enums, namespaces and functions. Class members are not expanded here - use list_methods or list_functions for those.
Analyzes all TypeScript/JavaScript files in a directory, providing a package-level summary
Generates a Mermaid flowchart showing the call graph of functions in a TypeScript/JavaScript file or directory
Computes cyclomatic complexity for functions in a TypeScript/JavaScript file
Finds unreferenced module-local symbols within a directory: unexported functions, types and variables, plus 'private' and '#name' class members. Reports a symbol never named anywhere but its own declaration.
Compares two TypeScript/JavaScript files structurally, reporting added/removed/modified symbols
Output schemas not documented. LLMs cannot predict return structure (FileSymbol[], Finding[], ComplexityResult[], DiffEntry[], etc.). Forces agents to guess field names and types.
Enum parameters (direction: TD|LR, scope: file|package) lack formal enum constraints in schema. Described in text only; LLMs may hallucinate invalid values.
No pagination support for tools returning potentially large result sets (analyze_package, dead_code, call_graph). Results could exceed context window; no limit or cursor documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Analyzes TypeScript-specific error patterns: floating promises, empty catches, unsafe type assertions, double assertions
Finds all functions in a file or package that call the specified function (reverse call graph)
Extracts JSDoc/TSDoc comments for a symbol (function, type, class, variable). Supports Class.method syntax.
Error handling via safeTool wrapper returns generic error messages. No recovery guidance (e.g., 'file not found, check path' or 'syntax error, fix and retry'). Agents cannot self-correct.
No tool annotations (readOnlyHint). All tools are read-only but this is not declared in schema. Agents cannot distinguish safe tools from destructive ones.