Swisstransport

The ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) has genuinely overlapping purposes — the beta tool's own description admits it 'currently matches ask_pipeworx exactly,' making selection arbitrary. The polymarket cluster (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) and the discovery cluster (discover_tools, suggest_questions, pipeworx_trending) are distinguishable only after reading long descriptions, and the three Swiss-transport tools sit in an otherwise unrelated surface.

Names are uniformly snake_case and follow a predictable verb_noun or domain_prefix pattern (get_connections, search_stations, resolve_entity, polymarket_edges, ask_pipeworx_grounded). The domain prefixes (polymarket_, ask_pipeworx_, pipeworx_) are used consistently, though a few noun-only names (entity_profile, recent_changes, deep_research) break the strict verb_noun pattern.

34 tools is heavy and, more tellingly, wildly mismatched to the 'swisstransport' identity — only three tools (search_stations, get_stationboard, get_connections) serve transport, while 31 are Pipeworx gateway/meta tools bolted onto the same server. That is far more surface than the named purpose warrants.

For the transport domain the core lifecycle is present (station search, live departure board, point-to-point connections), covering the primary workflows. Minor gaps remain (no ticket/fare, no disruption or route-detail lookups), but an agent can accomplish the common Swiss-transit tasks without a dead end.