Skip to main content
Glama
reallygood83

UI Expert MCP Server

by reallygood83

analyze_ui

Analyze UI/UX interfaces to identify issues and provide improvement recommendations based on framework compatibility, target audience needs, and design requirements.

Instructions

Analyze current UI/UX and provide improvement recommendations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameworkYesFrontend framework
currentIssuesYesList of current UI/UX issues
targetAudienceNoTarget user demographic
designStyleNoDesired design style

Implementation Reference

  • The primary handler function that generates a detailed UI/UX analysis report including recommendations for design system, components, accessibility, performance, and responsive design.
    function generateUIAnalysis(params: z.infer<typeof AnalyzeUISchema>): string {
      const { framework, currentIssues, targetAudience, designStyle } = params;
      
      return `# UI/UX Analysis Report
    
    ## Current Framework: ${framework}
    
    ## Identified Issues:
    ${currentIssues.map(issue => `- ${issue}`).join('\n')}
    
    ## Recommendations:
    
    ### 1. Design System Implementation
    - Create a comprehensive design token system
    - Implement consistent spacing, typography, and color scales
    - Use CSS custom properties for easy theming
    
    ### 2. Component Architecture
    - Refactor into smaller, reusable components
    - Implement proper component composition patterns
    - Add loading and error states
    
    ### 3. Accessibility Improvements
    - Ensure WCAG 2.1 AA compliance
    - Add proper ARIA labels and roles
    - Implement keyboard navigation
    - Ensure sufficient color contrast
    
    ### 4. Performance Optimization
    - Implement lazy loading for heavy components
    - Use React.memo() or equivalent for expensive renders
    - Optimize bundle size with code splitting
    
    ### 5. Responsive Design
    - Mobile-first approach
    - Use modern CSS Grid and Flexbox
    - Implement fluid typography and spacing
    
    ${targetAudience ? `\n### Target Audience Considerations:\n- ${targetAudience}` : ''}
    ${designStyle ? `\n### Design Style Direction:\n- ${designStyle}` : ''}`;
    }
  • Zod schema defining the input parameters for the analyze_ui tool: framework (required), currentIssues (required), targetAudience (optional), designStyle (optional).
    const AnalyzeUISchema = z.object({
      framework: z.string().describe("Frontend framework (react, vue, angular, etc)"),
      currentIssues: z.array(z.string()).describe("List of current UI/UX issues"),
      targetAudience: z.string().optional().describe("Target user demographic"),
      designStyle: z.string().optional().describe("Desired design style (modern, minimal, corporate, etc)"),
    });
  • src/index.ts:58-75 (registration)
    Registration of the analyze_ui tool in the ListToolsRequestHandler response, specifying name, description, and JSON schema matching the Zod schema.
    {
      name: "analyze_ui",
      description: "Analyze current UI/UX and provide improvement recommendations",
      inputSchema: {
        type: "object",
        properties: {
          framework: { type: "string", description: "Frontend framework" },
          currentIssues: { 
            type: "array", 
            items: { type: "string" },
            description: "List of current UI/UX issues" 
          },
          targetAudience: { type: "string", description: "Target user demographic" },
          designStyle: { type: "string", description: "Desired design style" },
        },
        required: ["framework", "currentIssues"],
      },
    },
  • Dispatch handler in CallToolRequestHandler that parses input arguments using AnalyzeUISchema and invokes the generateUIAnalysis function to produce the tool response.
    case "analyze_ui": {
      const parsed = AnalyzeUISchema.parse(args);
      return {
        content: [
          {
            type: "text",
            text: generateUIAnalysis(parsed),
          },
        ],
      };
    }
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 mentions the action 'analyze' and outcome 'provide improvement recommendations', but lacks details on permissions, rate limits, output format, or whether it's read-only or mutative. This is inadequate for a tool with no annotation coverage.

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 front-loads the core purpose. It avoids redundancy and waste, though it could be slightly more structured by separating analysis from recommendations. Overall, it's appropriately sized for the tool's complexity.

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 no annotations, no output schema, and 4 parameters, the description is incomplete. It doesn't explain what the recommendations look like, how they're generated, or any behavioral traits. For a tool that likely involves analysis and suggestions, more context is needed to guide the agent effectively.

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%, so the schema already documents all four parameters with descriptions. The description adds no additional meaning or context beyond what the schema provides, such as how parameters interact or examples of usage. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description states the tool's purpose as analyzing UI/UX and providing recommendations, which is clear but vague. It specifies the verb 'analyze' and resource 'current UI/UX' with the outcome 'improvement recommendations', but doesn't differentiate from sibling tools like 'improve_component' or 'generate_design_tokens', leaving ambiguity about scope.

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 alternatives. With sibling tools like 'improve_component' and 'generate_design_tokens', there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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/reallygood83/ui-expert-mcp'

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