Brokercheck

Most tools have clearly distinct purposes, but `ask_pipeworx` and `ask_pipeworx_beta` are nearly identical (explicitly stated as the same router with experimental routing), and `discover_tools` and `suggest_questions` overlap in intent. The rest of the tools (Polymarket, memory, subscriptions) are well-differentiated.

Naming conventions are mixed: some tools use snake_case (`ask_pipeworx`, `company_facts`), some camelCase (`ai_visibility_check`, `deep_research`), and verbs vary widely (`ask`, `search`, `scan`, `compare`, `resolve`, `remember`). The `polymarket_*` group is consistent internally, but overall there is no predictable pattern, making it hard to guess tool names.

With 39 tools, this is a heavy surface. The server name 'Brokercheck' suggests a focused financial tool, but it actually provides a broad data aggregation service (news, weather, sports, memory, subscriptions). Many tools are tangential to the implied purpose, and the count exceeds the reasonable range for the apparent scope.

The broker-specific functionality is minimal but covers search and detail for individuals and firms, which is the core need. However, the server's broader data surface lacks obvious lifecycle operations (e.g., no export or bulk reporting), and there is no tool to compare brokers side-by-side or track changes over time. The coverage is adequate for read-only inquiries but has notable gaps.