Gurufocus

Many tools serve distinct purposes (e.g., entity_profile vs company_facts vs compare_entities), but there is significant overlap among the Polymarket edge tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research) and among the query routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research). These require careful reading of long descriptions to select correctly.

Most tools use descriptive snake_case names (entity_profile, compare_entities, resolution_audit, etc.), but naming patterns are mixed: some are domain-prefixed (polymarket_*, gurufocus_*, pipeworx_*), some are generic verbs (remember, recall, forget, subscribe), and some are noun phrases (company_facts, recent_changes). The style is consistent snake_case but the conceptual pattern varies.

40 tools is a very large surface for a single MCP server, and many appear to be meta-tools or thin wrappers around a larger Pipeworx catalog (ask_pipeworx, discover_tools, suggest_questions). This exceeds the typical well-scoped range and creates cognitive load for agents.

The server covers a broad domain (financial data, prediction markets, AI visibility, memory, subscriptions) quite thoroughly, including lifecycle operations (subscribe/unsubscribe, remember/recall/forget, resolution_audit/diff). Minor gaps exist (e.g., no direct tool to create or edit a Polymarket market, no bulk export), but most workflows have no dead ends.