Coinglass

Several tool clusters have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same underlying catalog; polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, and bet_research all analyze prediction-market opportunities. Descriptions attempt to differentiate them, but at a glance an agent can easily misselect among these near-identical entry points.

Almost every tool uses snake_case, which is a consistent convention. Prefixes like coinglass_, polymarket_, and pipeworx_ are applied unevenly, and some tools are noun phrases (entity_profile, company_facts) while others are verb phrases (ask_pipeworx, validate_claim), but the overall naming is predictable and readable.

40 tools is heavy for a single MCP server and spans crypto data, prediction markets, company financials, AI visibility, memory, subscriptions, and meta-gateway operations. Even if the server is a broad Pipeworx gateway, the count is large enough to overwhelm tool selection and feels like several servers merged into one.

The surface covers a wide range: universal question routing, grounded research, company/drug entity resolution, prediction-market analysis, memory CRUD (remember/recall/forget), subscriptions (subscribe/list/unsubscribe/alerts), and feedback. Minor gaps exist (e.g., no direct tool to call an arbitrary underlying data tool without going through a router, and only four Coinglass-specific metrics), but most core workflows are supported.