Loading ToolBench
Design-Theory-as-a-Service MCP server — anti-slop quality gates, WCAG audits, OKLCH token engine, motion.dev integration, and tri-agent skills.
Server has 26 tools with mostly complete schemas and descriptions. Naming follows verb_noun convention well (generate_*, list_*, get_*, validate_*, etc.). Descriptions are present and contextual (avg ~150 chars), though some lack actionable guidance. All tools have input schemas with type definitions. However, output schemas are not documented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance or categorization. Tool composition is reasonable but some tools combine multiple concerns (e.g., generate_rules handles style+palette+archetype+hybrid in one call). No tool annotations (readOnlyHint/destructiveHint) despite clear read/write distinction. Parameter descriptions are adequate but some lack format/constraint details (e.g., 'style' enum is documented in description, not schema constraint).
Run a comprehensive WCAG accessibility audit on HTML content. Checks for alt text, labels, heading order, color contrast, focus management, and more. Returns issues with severity levels and fix instructions.
Download and return the DESIGN.md for a real brand (stripe, vercel, linear, notion, claude, tesla, etc.).
Build custom design tokens from a base palette and configuration. Supports OKLCH color space, semantic naming, and multi-theme generation.
Detect the design genre of HTML/CSS content (editorial, modern-minimal, atmospheric, playful, etc.).
Evaluate which design style best fits your product context (brand, industry, audience, tone). Returns ranked recommendations with reasoning.
Export a complete design system project as a ZIP file with all assets, tokens, components, and documentation.
No output schemas documented. LLMs cannot predict response structure, forcing them to guess at field names and types for downstream tool chaining. This violates pattern:tool and pattern:response-shaper.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Server clearly distinguishes read-only vs write tools (export_project is WRITE), but LLMs cannot see this distinction in the schema. Violates pattern:tool-annotation.
Minimal error handling and no recovery guidance. Tools like palette_fetch (external API) and brand_fetch_design_md (network call) have no documented error cases, timeouts, or retry strategies. Violates pattern:recovery-guide.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Generate an interactive 8-state component demo (button, input, toggle, chip, select) showing default, hover, focus, active, disabled, loading, error, and success states.
Generate CSS output in multiple formats (standard CSS, CSS-in-JS, Tailwind, SCSS, PostCSS) from design tokens and rules.
Generate motion.dev animation snippets for React/Vue/Svelte with spring physics and gesture support.
Generate anime.js v3 animation snippets for a design style. Categories: entrance, micro, stagger, scroll, loader, transition, counter, typewriter.
Generate accessible color variants (lighter, darker, saturated, desaturated) from a base palette using OKLCH.
Generate design rules for a style + palette + optional archetype/hybrid. IMPORTANT: Run evaluate_style first to determine the best style for your product context. Only use this tool after evaluation confirms the style choice.
Generate a ready-to-use tailwind.config.js for a design style + palette combination. Returns the full config object and module.exports code string.
Generate a full HTML starter page for a style + palette + archetype combination.
Generate design tokens (color, typography, spacing, shadow, radius) for a style + palette combination in multiple formats (CSS, JSON, Figma, Tailwind).
Get a single component (button, card, input, etc.) for a style + palette, optionally with framework output (React, Vue, Svelte, Web Components).
Return the full content of a reference document by name (e.g. 'ant-design', 'accessibility', 'design-tokens', 'getdesign-md').
List all available design genres (editorial, modern-minimal, atmospheric, playful, etc.).
List all available design systems, palettes, archetypes, and valid hybrid combinations.
List all available design themes and their characteristics.
Convert palette JSON from palette_fetch into CSS, Tailwind, SCSS, Figma tokens, Android XML, or Swift.
Fetch live color palettes from Color Hunt.
Run anti-slop quality gates on HTML/CSS content. Detects AI-generated design tells, templated patterns, and low-effort design choices.
Scan an HTML/CSS project for design system compliance, anti-patterns, and accessibility issues. Returns a detailed audit report.
Generate a self-critique of a design based on anti-slop gates and design theory. Returns actionable feedback for improvement.
Validate a style + palette + optional hybrid combination before generating rules.
Enum constraints documented in descriptions, not in JSON Schema. Parameter 'style' lists valid values in description text ('ant|carbon|fluent|...') rather than as schema enum. LLMs cannot parse description text for constraints; they need formal schema enums. Violates pattern:constrained-input.
Tool composition: generate_rules combines style + palette + archetype + hybrid + tailwind in one call. This couples multiple concerns and forces the LLM to reason about all parameters even when only style+palette are needed. Consider splitting into generate_rules (core) and optional modifiers (add_archetype, add_hybrid).