UX/UI Tools for React + Material-UI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apply_responsivenessC | Aplica responsividade mobile-first em componente React/MUI |
| apply_material_ui_best_practicesC | Aplica best practices do Material-UI (theme.spacing, alpha, sx prop) |
| apply_apple_designC | Aplica padrões de design Apple (scrollbar, animações, minimalismo) |
| apply_nielsen_heuristicC | Aplica uma heurística específica de Nielsen |
| apply_cognitive_biasC | Aplica viés cognitivo específico para melhor UX |
| apply_complete_uxC | Aplica TODAS as diretrizes de UX/UI (responsividade, MUI, Apple, Nielsen, vieses) |
| get_ux_checklistB | Retorna checklist de UX/UI para validação |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Multiple tools have overlapping purposes that will cause confusion. For example, 'apply_complete_ux' appears to encompass functionality covered by other tools like 'apply_apple_design', 'apply_nielsen_heuristic', and 'apply_responsiveness', creating ambiguity about when to use which tool. While some tools target specific domains (e.g., Apple design vs. Material-UI), the boundaries between them are unclear, especially with the broad 'apply_complete_ux' tool.
The naming follows a mostly consistent 'verb_noun' pattern with 'apply_' or 'get_' prefixes, which is predictable and readable. However, there is a minor deviation with 'get_ux_checklist' using 'get_' instead of 'apply_', but this is reasonable given its different action. Overall, the naming is coherent with only slight variations.
With 7 tools, the count is reasonable and well-scoped for a UX/UI-focused server, avoiding being too thin or heavy. Each tool appears to target a specific aspect of UX/UI design, such as design systems, heuristics, or responsiveness, which justifies their inclusion. A slight reduction might improve clarity, but the number is appropriate.
The tool set covers key UX/UI domains like design systems (Apple, Material-UI), heuristics (Nielsen), and responsiveness, but there are notable gaps. For instance, it lacks tools for user testing, accessibility checks, or performance optimization, which are common in UX/UI workflows. While core areas are addressed, the surface is not fully comprehensive for the stated purpose of React + Material-UI tools.