Skip to main content
Glama

apply_responsiveness

Apply mobile-first responsive design to React/Material-UI components by analyzing code and implementing breakpoints for optimal viewing across devices.

Instructions

Aplica responsividade mobile-first em componente React/MUI

Input Schema

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

Implementation Reference

  • Handler logic for the 'apply_responsiveness' tool. Returns formatted text with UX guidelines for responsiveness, including instructions and example tailored to the provided component.
    case 'apply_responsiveness':
      return {
        content: [
          {
            type: 'text',
            text: `${UX_GUIDELINES.responsividade.instructions}\n\n**Exemplo:**\n${UX_GUIDELINES.responsividade.example}\n\n**Componente:** ${args.component}`,
          },
        ],
      };
  • index.js:403-416 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema requiring a 'component' string.
    {
      name: 'apply_responsiveness',
      description: 'Aplica responsividade mobile-first em componente React/MUI',
      inputSchema: {
        type: 'object',
        properties: {
          component: {
            type: 'string',
            description: 'Código do componente ou nome do arquivo',
          },
        },
        required: ['component'],
      },
    },
  • Helper data structure defining the instructions and example code snippet for applying responsiveness guidelines, referenced by the tool handler.
      responsividade: {
        description: "Torna componente responsivo e mobile-friendly",
        instructions: `
    **Responsividade Mobile-First:**
    
    1. Use useMediaQuery do MUI:
       \`\`\`typescript
       import { useMediaQuery, useTheme } from '@mui/material';
       const theme = useTheme();
       const isMobile = useMediaQuery(theme.breakpoints.down('sm'));
       \`\`\`
    
    2. Dimensões adaptativas:
       - Mobile: calc(100vw - 16px) ou 100%
       - Desktop: valores fixos (420px, 600px, etc.)
    
    3. Touch targets mínimo 44x44px:
       \`\`\`typescript
       <IconButton sx={{ minWidth: 44, minHeight: 44 }}>
       \`\`\`
    
    4. Breakpoints MUI:
       - xs: 0px (mobile pequeno)
       - sm: 600px (mobile grande/tablet)
       - md: 900px (tablet grande)
       - lg: 1200px (desktop)
       - xl: 1536px (desktop grande)
    
    5. Transições por dispositivo:
       - Mobile: Slide up
       - Desktop: Slide down ou Fade
        `,
        example: `
    const isMobile = useMediaQuery(theme.breakpoints.down('sm'));
    
    <Box
      sx={{
        width: isMobile ? 'calc(100vw - 16px)' : 420,
        height: isMobile ? '70vh' : 'min(600px, 80vh)',
      }}
    >
      <Slide direction={isMobile ? 'up' : 'down'}>
        {children}
      </Slide>
    </Box>
        `
      },
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 mobile-first responsiveness, implying a mutation or transformation, but doesn't describe what this entails (e.g., modifies code in-place, creates a new version, requires specific permissions). It also lacks details on side effects, error handling, or output format, leaving significant gaps in understanding how the tool behaves.

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

Conciseness5/5

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

The description is a single, efficient sentence in Portuguese that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence earns its place by conveying essential information concisely.

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 complexity of applying responsiveness (a mutation operation) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns, how changes are applied, or any behavioral traits like error conditions. For a tool that likely modifies code, more context is needed to understand its full impact and usage.

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?

The input schema has 100% description coverage, with one parameter 'component' documented as 'Código do componente ou nome do arquivo' (Component code or file name). The description doesn't add any meaning beyond this, such as examples or constraints. With high schema coverage, the baseline is 3, as the schema adequately handles parameter documentation without extra value from the description.

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: 'Aplica responsividade mobile-first em componente React/MUI' (Applies mobile-first responsiveness to a React/MUI component). It specifies the verb ('aplica'), resource ('componente React/MUI'), and scope ('responsividade mobile-first'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'apply_material_ui_best_practices' or 'apply_complete_ux', which might also involve UI/UX improvements.

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. It doesn't mention prerequisites, such as needing a React/MUI component, or compare it to siblings like 'apply_material_ui_best_practices' or 'apply_complete_ux', which could overlap in functionality. Usage is implied by the purpose but lacks explicit context 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