Space Feeds

Several tool families overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded route the same question, and the description admits beta currently matches the stable router exactly, so an agent has little basis to choose among them. discover_tools and suggest_questions also both serve a 'what can I do' discovery role, and the six polymarket tools share prediction-market territory though their purposes are mostly differentiable.

All names are consistently snake_case with no camelCase/snake_case mixing, which keeps them readable. However, styles vary between verb_noun (compare_entities, resolve_entity, validate_claim, fetch_feed), noun_verb (ai_visibility_check), and namespaced groups (polymarket_*, ask_pipeworx_*, pipeworx_*), so the convention is readable but not uniform.

At 34 tools this sits well above the heavy threshold, and the count is inflated by redundancy (three ask_pipeworx routing variants) plus a sprawling mix of unrelated domains (prediction markets, memory, feeds, AI-marketing, npm scanning) under a 'Space Feeds' name. The breadth is real, but the set is over-large and could be consolidated.

Coverage is strong across its apparent domains: full memory CRUD (remember/recall/forget), subscription lifecycle (subscribe/unsubscribe/list/recent_alerts), feed access (list/read/fetch), entity resolution and profiling, claim validation, and a deep prediction-market suite (research, arbitrage, edges, tracker, fill risk, cross-venue). Only minor gaps remain, such as no explicit subscription-update operation and no direct generic tool-invocation beyond the router meta-tools.