Skip to main content
Glama

list_web_components

Retrieve web accessibility components from MagentaA11y with optional category filtering to support development of accessible interfaces.

Instructions

List all available web accessibility components from MagentaA11y. Optionally filter by category (e.g., controls, forms, components).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional category filter (e.g., "controls", "forms", "components")

Implementation Reference

  • Core handler function that executes the list_web_components tool logic by calling contentLoader to list web components and categories, then formats the response as MCP content.
    async function handleListWebComponents(args: any) {
      const components = contentLoader.listComponents('web', args?.category);
      const categories = contentLoader.getCategories('web');
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                components,
                categories,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Input schema and metadata definition for the list_web_components tool, used for MCP tool listing and validation.
      name: 'list_web_components',
      description: 'List all available web accessibility components from MagentaA11y. Optionally filter by category (e.g., controls, forms, components).',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Optional category filter (e.g., "controls", "forms", "components")',
          },
        },
      },
    },
  • src/index.ts:36-40 (registration)
    Registers the tool list handler which exposes list_web_components in the MCP tools/list response.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: TOOL_DEFINITIONS,
      };
    });
  • src/index.ts:50-51 (registration)
    Dispatch registration in the main CallToolRequestSchema switch statement that routes calls to the handler.
    case 'list_web_components':
      return await handleListWebComponents(args);
  • Inline handler implementation for the Netlify HTTP transport version of the MCP server.
    case 'list_web_components': {
      const components = contentLoader.listComponents('web', args?.category);
      const categories = contentLoader.getCategories('web');
      return { content: [{ type: 'text', text: JSON.stringify({ components, categories }, null, 2) }] };
    }
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 describes a read operation ('List') but lacks details on permissions, rate limits, pagination, or response format. This leaves significant gaps in understanding how the tool behaves beyond basic functionality.

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 that front-loads the core action ('List all available web accessibility components') and includes optional filtering details without unnecessary elaboration. Every part of the sentence serves a clear purpose, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns a list of components. It does not explain the return format, such as whether it includes IDs, names, or other metadata, nor does it address potential limitations or error handling, leaving key contextual gaps.

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, clearly documenting the optional 'category' parameter. The description adds minimal value by mentioning filtering examples ('e.g., controls, forms, components'), which slightly enhances understanding but does not go beyond what the schema provides, aligning with the baseline score of 3.

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 verb ('List') and resource ('all available web accessibility components from MagentaA11y'), making the purpose specific and understandable. However, it does not explicitly differentiate this tool from its siblings like 'list_native_components' or 'get_web_component', which limits the score to 4 instead of 5.

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, such as 'list_native_components' for native components or 'get_web_component' for detailed information on a specific component. It mentions optional filtering but does not specify scenarios or exclusions, resulting in minimal usage guidance.

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/joe-watkins/magentaa11y-mcp-remote'

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