Skip to main content
Glama

search_web_criteria

Search web accessibility criteria by keywords to find WCAG guidelines, implementation patterns, and specific requirements for accessible web development.

Instructions

Search web accessibility criteria using keywords. Find criteria related to WCAG guidelines, implementation patterns, or specific accessibility requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch term or phrase (e.g., "focus indicator", "aria-label")
max_resultsNoMaximum number of results to return (default: 10)

Implementation Reference

  • Main handler function for search_web_criteria tool. Calls contentLoader.search('web', query, maxResults) and returns JSON-formatted results.
    async function handleSearchWebCriteria(args: any) {
      const maxResults = args?.max_results || 10;
      const results = await contentLoader.search('web', args.query, maxResults);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(results, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and input schema for search_web_criteria.
    {
      name: 'search_web_criteria',
      description: 'Search web accessibility criteria using keywords. Find criteria related to WCAG guidelines, implementation patterns, or specific accessibility requirements.',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search term or phrase (e.g., "focus indicator", "aria-label")',
          },
          max_results: {
            type: 'number',
            description: 'Maximum number of results to return (default: 10)',
            default: 10,
          },
        },
        required: ['query'],
      },
    },
  • Inline handler for search_web_criteria in Netlify HTTP transport. Directly calls contentLoader.search.
    case 'search_web_criteria': {
      const results = await contentLoader.search('web', args.query, args.max_results || 10);
      return { content: [{ type: 'text', text: JSON.stringify(results, null, 2) }] };
  • src/index.ts:36-40 (registration)
    Registers the list tools handler that returns TOOL_DEFINITIONS including search_web_criteria.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: TOOL_DEFINITIONS,
      };
    });
  • src/index.ts:54-55 (registration)
    Dispatch case in CallToolRequestSchema handler that routes to the search_web_criteria handler.
    case 'search_web_criteria':
      return await handleSearchWebCriteria(args);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions searching but doesn't disclose behavioral traits like whether this is a read-only operation, how results are ranked/limited, error conditions, or performance characteristics. The description is functional but lacks transparency about how the tool behaves beyond the basic action.

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 extremely concise (two sentences) and front-loaded with the core purpose. Every sentence earns its place: the first states the action and scope, the second provides concrete examples. There's zero wasted text or redundancy.

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 moderate complexity (search operation with 2 parameters), 100% schema coverage, but no annotations or output schema, the description is minimally complete. It covers what the tool does and provides examples, but lacks details about return format, error handling, or behavioral constraints that would be helpful for an agent.

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 both parameters (query and max_results) thoroughly. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter explanation.

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: 'Search web accessibility criteria using keywords' with specific examples of what can be searched (WCAG guidelines, implementation patterns, accessibility requirements). It distinguishes from sibling tools by focusing on 'web' accessibility criteria rather than native components, though it doesn't explicitly contrast with 'search_native_criteria'.

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

Usage Guidelines3/5

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

The description implies usage context through the examples ('WCAG guidelines, implementation patterns, or specific accessibility requirements'), suggesting this tool is for finding accessibility standards. However, it doesn't provide explicit guidance on when to use this versus the sibling 'search_native_criteria' tool or other search/list tools, nor does it mention prerequisites 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/joe-watkins/magentaa11y-mcp-remote'

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