Skip to main content
Glama

apply_complete_ux

Apply comprehensive UX/UI guidelines including responsive design, Material-UI patterns, Apple design principles, Nielsen heuristics, and cognitive biases to React components.

Instructions

Aplica TODAS as diretrizes de UX/UI (responsividade, MUI, Apple, Nielsen, vieses)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentYesCódigo do componente ou nome do arquivo

Implementation Reference

  • Handler for the 'apply_complete_ux' tool. Returns a text response containing the complete UX guidelines instructions from UX_GUIDELINES.completeUX, appended with the target component name and a note to apply all guidelines.
    case 'apply_complete_ux':
      return {
        content: [
          {
            type: 'text',
            text: `${UX_GUIDELINES.completeUX.instructions}\n\n**Componente:** ${args.component}\n\nAplique TODAS as diretrizes acima no componente especificado.`,
          },
        ],
      };
  • index.js:483-496 (registration)
    Registration of the 'apply_complete_ux' tool in the ListToolsRequestSchema response. Includes the tool name, description, and input schema requiring a 'component' string parameter.
    {
      name: 'apply_complete_ux',
      description: 'Aplica TODAS as diretrizes de UX/UI (responsividade, MUI, Apple, Nielsen, vieses)',
      inputSchema: {
        type: 'object',
        properties: {
          component: {
            type: 'string',
            description: 'Código do componente ou nome do arquivo',
          },
        },
        required: ['component'],
      },
    },
  • Helper data object UX_GUIDELINES.completeUX containing the description and detailed instructions/checklist used by the tool handler to provide comprehensive UX/UI guidelines.
      completeUX: {
        description: "Aplica TODAS as diretrizes de UX/UI",
        instructions: `
    **Checklist Completo:**
    
    ✅ Responsividade Mobile-First
    ✅ Material-UI Best Practices
    ✅ Apple Design Patterns
    ✅ 10 Heurísticas de Nielsen
    ✅ Vieses Cognitivos (Fitts, Grouping, Proximity, etc.)
    
    **Aplique:**
    1. useMediaQuery para responsividade
    2. theme.spacing para espaçamentos
    3. alpha() para transparências
    4. Tooltips em todos botões/ícones
    5. Loading states em ações
    6. Mensagens de erro claras
    7. Touch targets ≥ 44px
    8. Transições suaves
    9. Scrollbar customizada
    10. Validação em tempo real
        `
      }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool applies guidelines but doesn't describe how it works (e.g., modifies code, generates reports, requires specific permissions), what happens to the component, or any side effects like overwriting existing styles. This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that lists the guidelines covered. It's front-loaded with the core action and avoids unnecessary words, though it could be slightly more structured by separating the guideline list for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (applying multiple UX/UI guidelines to a component), lack of annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how changes are applied, or any behavioral traits like error handling or performance impact, leaving the agent with incomplete information for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'component' documented as 'Código do componente ou nome do arquivo'. The description adds no additional meaning about this parameter beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: applying all UX/UI guidelines including responsiveness, MUI, Apple, Nielsen, and biases. It uses a specific verb ('Aplica') and identifies the scope ('TODAS as diretrizes de UX/UI'), though it doesn't explicitly distinguish from siblings like apply_apple_design or apply_responsiveness that handle subsets of these guidelines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings. It lists the guidelines covered but doesn't indicate scenarios where applying all guidelines is preferable to using individual tools like apply_apple_design or apply_nielsen_heuristic, nor does it mention prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MarcusViniciusBarcelos/uiux-tools-react-mui'

If you have feedback or need assistance with the MCP directory API, please join our Discord server