numuersapi

Several tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to data sources with subtle differences; entity_profile, compare_entities, and recent_changes all pull company data; ai_visibility_check and scan_competitor_ai_presence probe LLM brand visibility. Though descriptions attempt to distinguish them, the boundaries are fine-grained and an agent could easily pick the wrong tool.

Most tools use snake_case with a verb or noun prefix, but conventions vary: verb-led (ask_pipeworx, list_subscriptions, validate_claim) mix with noun-led (entity_profile, polymarket_arbitrage, pipeworx_trending) and adjective-led (recent_alerts). The polymarket_* and pipeworx_* prefixes provide some consistency within families, but there's no uniform verb_noun pattern across the set.

With 31 tools, the set is large and will strain model context; many tools could be consolidated (the six polymarket tools, the four ask/deep-research variants, the three memory tools). This exceeds the 25+ threshold that typically degrades usability.

The surface covers querying, entity resolution, research, alerts/subscriptions, memory, feedback, and specialized checks (dependency, AI visibility, claim verification). The main gap is no way to update an existing subscription (only create/list/cancel), but overall the domain is well covered with few dead ends.