Skip to main content
Glama

list_native_components

Retrieve native iOS/Android accessibility components from MagentaA11y. Filter by category to find specific controls or components for accessibility testing and development.

Instructions

List all available native (iOS/Android) accessibility components from MagentaA11y. Optionally filter by category.

Input Schema

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

Implementation Reference

  • Primary handler function for the list_native_components tool. Lists native accessibility components and categories using ContentLoader, optionally filtered by category, and returns a JSON-formatted MCP response.
    async function handleListNativeComponents(args: any) {
      const components = contentLoader.listComponents('native', args?.category);
      const categories = contentLoader.getCategories('native');
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                components,
                categories,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and input schema allowing an optional category filter.
    {
      name: 'list_native_components',
      description: 'List all available native (iOS/Android) accessibility components from MagentaA11y. Optionally filter by category.',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Optional category filter (e.g., "controls", "components")',
          },
        },
      },
    },
  • src/index.ts:36-40 (registration)
    Registers the MCP list tools handler to return TOOL_DEFINITIONS, which includes list_native_components.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: TOOL_DEFINITIONS,
      };
    });
  • Alternative inline handler for list_native_components in the Netlify HTTP transport implementation.
    case 'list_native_components': {
      const components = contentLoader.listComponents('native', args?.category);
      const categories = contentLoader.getCategories('native');
      return { content: [{ type: 'text', text: JSON.stringify({ components, categories }, null, 2) }] };
  • src/index.ts:56-57 (registration)
    Dispatch case in the MCP CallToolRequestSchema handler that routes to the list_native_components handler function.
    case 'list_native_components':
      return await handleListNativeComponents(args);
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 listing components and optional filtering, but does not cover critical aspects such as pagination behavior, rate limits, authentication needs, or what the output format looks like (e.g., list structure, fields included). This is a significant gap 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.

Conciseness5/5

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

The description is front-loaded with the core purpose and efficiently includes the optional filtering detail in a single, clear sentence. There is no wasted text, making it appropriately sized and easy to parse.

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

Completeness3/5

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

Given the tool's low complexity (1 optional parameter, no output schema, no annotations), the description is somewhat complete but lacks depth. It covers the basic purpose and parameter use, but without annotations or output schema, it should ideally include more behavioral context (e.g., response format, limitations) to fully guide the agent, resulting in an adequate but not thorough description.

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 description adds minimal value beyond the input schema, which has 100% coverage for the single parameter 'category'. It mentions 'Optionally filter by category', aligning with the schema's description, but does not provide additional semantics like example categories beyond 'controls' or 'components' or explain how filtering works. 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.

Purpose5/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 ('native (iOS/Android) accessibility components from MagentaA11y'), making the purpose specific. It also distinguishes from siblings like 'list_web_components' by specifying 'native' components and from 'get_native_component' by indicating a list operation rather than retrieving a single component.

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

Usage Guidelines4/5

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

The description provides clear context for usage by mentioning optional filtering by category, which helps guide when to use this tool. However, it does not explicitly state when not to use it or name alternatives (e.g., 'search_native_criteria' for more complex queries), leaving room for improvement in sibling differentiation.

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