Related Servers

Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized by target platform (web vs. native) and action type (get details, list components, search criteria), making it easy for an agent to select the right tool for the task. For example, get_web_component retrieves detailed criteria for a specific web component, while search_web_criteria performs keyword searches across web criteria.

Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. The naming convention clearly indicates the action (get, list, search) and the target resource (component, criteria), with platform prefixes (web_ or native_) where applicable. This predictability makes the tool set easy to navigate and understand.

With 11 tools, the count is well-scoped for the server's purpose of providing accessibility criteria and components. Each tool earns its place by covering distinct aspects like retrieval, listing, and searching across web and native platforms, without redundancy. This number supports comprehensive functionality while remaining manageable.

The tool surface offers complete coverage for the accessibility domain, with no obvious gaps. It includes CRUD-like operations (get details, list components, search criteria) for both web and native platforms, along with specialized formats (condensed, developer notes, Gherkin). This ensures agents can handle various accessibility tasks without dead ends.