Scored across 40 tools
Most tools are separated by clear resource/action namespaces, but the large set of search tools (layout.search, part.search, motion.search, background.search, narrative.search, responsive.search, design.search_by_image, design.similar_site, search.unified) creates overlapping boundaries. Batch/analyze tools such as layout.batch_ingest, page.batch_analyze, page.analyze, and layout.ingest also require careful reading to distinguish.
The tool set predominantly follows a namespace.action or namespace.verb pattern with snake_case actions, which is readable and predictable. Minor deviations include camelCase action names such as page.getJobStatus and page.getBatchStatus alongside snake_case tools like page.batch_analyze.
Forty tools is heavy for an MCP server and exceeds the practical range for reliable tool selection. While the platform has broad scope, several tools overlap or are deprecated, suggesting the surface could be consolidated substantially.
The server covers a wide design-analysis lifecycle: ingestion, inspection, semantic search, code generation, quality/accessibility/performance evaluation, reporting, preferences, and GDPR-oriented data controls. Minor gaps remain around managing stored entities and jobs, such as palette mutation or explicit cancel/list operations.
