Auto-generate 14 UML diagram types from codebase using AST analysis, LLM enrichment, and Kroki.io rendering
18 tools with consistent naming (verb_noun pattern: generate_*, render_*, select_*) and detailed parameter descriptions. All tools have descriptions (194-char baseline met). Schemas are present with type declarations and Field annotations. However, output schemas are not documented, LLMs cannot infer what fields to expect from responses. Error handling is absent: no guidance on retryable vs fatal failures, no recovery hints. Tool composition is weak: 14 diagram generators are near-duplicates differing only in diagram_type, violating single-responsibility. No pagination, no result limits documented despite potential for large AST scans. Security: no audit logging visible in tool definitions, though ENABLE_AUDIT_LOG env var exists in code.
Generate a UML activity diagram from project source code using AST analysis and LLM enrichment
Generate all 14 UML diagram types from project source code
Generate a call graph diagram from project source code using AST analysis
Generate a UML class diagram from project source code using AST analysis
Generate a UML communication diagram from project source code using LLM-powered analysis
Generate a UML component diagram from project source code using AST analysis
Generate a UML composite structure diagram from project source code using LLM-powered analysis
Output schemas not documented. LLMs cannot infer what fields diagram generation tools return (e.g., file_path, mermaid_code, error_details). This forces agents to guess and risks failed downstream chaining.
14 diagram generators are near-duplicates (generate_class_diagram, generate_sequence_diagram, etc.) differing only in diagram_type parameter. This violates single-responsibility and forces LLMs to reason about 14 similar tools. Consider a single generate_diagram(diagram_type, project_path, ...) tool with enum diagram_type.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Generate a UML deployment diagram from project source code using LLM-powered analysis
Generate a UML interaction overview diagram from project source code using LLM-powered analysis
Generate a UML object diagram from project source code using LLM-powered analysis
Generate a UML package diagram from project source code using AST analysis
Generate a UML sequence diagram from project source code using AST analysis and LLM enrichment
Generate a UML state machine diagram from project source code using AST analysis and LLM enrichment
Generate a UML timing diagram from project source code using LLM-powered analysis
Generate UML class diagram from code using AST analysis without LLM enrichment
Generate a UML use case diagram from project source code using LLM-powered analysis
Render a Mermaid diagram to SVG/PNG using Kroki.io
Select the best UML diagram type from a natural language description using keyword matching
No error handling guidance. Tools lack descriptions of failure modes (e.g., 'If project_path is invalid, returns error code 400 with message "Path not found". Verify path exists and is readable.'). Agents cannot distinguish retryable from fatal errors.
model_data parameter accepts JSON as a string but lacks validation guidance. Description says 'Max 512 KB' but does not explain what happens if exceeded, or how to validate before calling. No enum or pattern constraint on required keys (classes, nodes, steps, etc.).
render_diagram output_format parameter lacks enum constraint. Description lists 'svg, png, pdf' but does not enforce it as an enum, allowing LLMs to pass invalid formats like 'jpeg' or 'webp'.