A Model Context Protocol server for Angular project analysis and refactoring
The Angular Toolkit MCP provides 4 read-only design system tools with basic but incomplete schemas. Tool naming follows verb-noun convention (audit-, get-, list-) and is reasonably clear. All tools have non-empty descriptions (range 34-194 chars), meeting the 10-1024 char baseline. However, parameter descriptions are sparse or missing entirely for some params. Input schemas are present and use JSON Schema, but lack comprehensive validation constraints (e.g., enum definitions for directives). Output schemas are not documented, LLMs cannot predict what fields get_ds_component_data or list_ds_components return. Error handling is absent from visible tool code. No parameter validation guidance is visible. The codebase shows a well-structured tool hierarchy but falls short of production quality due to undocumented outputs and minimal error recovery patterns.
Audit token usage in style files for validity and overrides
List deprecated CSS classes for a DS component.
Return comprehensive data for a DS component including implementation files, documentation files, stories files, and import path.
List all available Design System components in the project. Returns component names, folder structures, import paths, implementation files, documentation files, and stories files.
Output schemas are not documented. LLMs cannot predict what fields these tools return (e.g., get_ds_component_data returns what structure? list_ds_components returns what array elements?). Without documented output schemas, agents must blind-guess field names for downstream operations.
Parameter descriptions are missing or generic. 'modes' param in audit-token-usage has an enum but no description of what each mode does or when to use them. 'excludePatterns' description is terse. 'sections' param in get-ds-component-data and list-ds-components repeats the enum but does not explain what each section reveals or why an agent should request one vs another.
No error handling guidance visible. Tool code does not show explicit error responses, recovery hints, or actionable error messages. If a directory does not exist or a component is not found, LLMs will receive a generic error and have no guidance on what to do next (retry? call a discovery tool instead?).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 55 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 50 | - | v1 |
Parameter validation constraints are incomplete. 'directory' and 'componentName' accept free-form strings with no format, regex, or length constraints documented. LLMs may pass invalid paths or non-existent component names without knowing the expected format.
No pagination or result limits documented. If list-ds-components returns hundreds of components, LLM context will be exhausted. No limit, page/offset, or cursor parameters are visible.