Skip to main content
Glama

search_native_criteria

Search platform-specific accessibility criteria for iOS VoiceOver and Android TalkBack to find implementation details for native mobile components.

Instructions

Search native accessibility criteria using keywords. Find platform-specific implementation details for iOS (VoiceOver) and Android (TalkBack).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term or phrase (e.g., "voiceover", "talkback", "accessibility label")
max_resultsNoMaximum number of results to return (default: 10)

Implementation Reference

  • Primary handler function that executes the search_native_criteria tool logic by invoking contentLoader.search on native platform criteria.
    async function handleSearchNativeCriteria(args: any) {
      const maxResults = args?.max_results || 10;
      const results = await contentLoader.search('native', args.query, maxResults);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(results, null, 2),
          },
        ],
      };
    }
  • Input schema, description, and tool definition used for registration and validation of search_native_criteria.
    {
      name: 'search_native_criteria',
      description: 'Search native accessibility criteria using keywords. Find platform-specific implementation details for iOS (VoiceOver) and Android (TalkBack).',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search term or phrase (e.g., "voiceover", "talkback", "accessibility label")',
          },
          max_results: {
            type: 'number',
            description: 'Maximum number of results to return (default: 10)',
            default: 10,
          },
        },
        required: ['query'],
      },
    },
  • Inline handler for search_native_criteria in the Netlify HTTP serverless function.
    case 'search_native_criteria': {
      const results = await contentLoader.search('native', args.query, args.max_results || 10);
      return { content: [{ type: 'text', text: JSON.stringify(results, null, 2) }] };
    }
  • src/index.ts:60-61 (registration)
    Switch case registration that routes tool calls to the search_native_criteria handler in the MCP stdio server.
    case 'search_native_criteria':
      return await handleSearchNativeCriteria(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. While it mentions the search functionality and platforms, it lacks details about permissions, rate limits, pagination, error handling, or what the results look like (especially since there's no output schema). This leaves significant gaps for a search tool.

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 two concise sentences with zero waste: the first states the action and mechanism, and the second specifies the context and differentiation. Every word earns its place, and it is front-loaded with the core purpose.

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 a search tool with no annotations and no output schema, the description is incomplete. It lacks information about result format, error conditions, or behavioral traits like rate limits. While it covers purpose and context well, it does not provide enough operational guidance for an AI agent to use it effectively without trial and error.

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 schema description coverage is 100%, so the schema already fully documents both parameters (query and max_results). The description adds no additional parameter semantics beyond what's in the schema, such as examples of effective queries or constraints on max_results. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Search') and resource ('native accessibility criteria'), specifies the search mechanism ('using keywords'), and distinguishes it from sibling tools by focusing on platform-specific iOS/Android details rather than web components or other formats mentioned in sibling names like 'search_web_criteria'.

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 when to use this tool ('Find platform-specific implementation details for iOS (VoiceOver) and Android (TalkBack)'), which implicitly differentiates it from web-focused alternatives. However, it does not explicitly state when NOT to use it or name specific alternative tools like 'search_web_criteria'.

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