Ffiec Call Reports

The server is named 'Ffiec Call Reports' but only 5 of 41 tools are FFIEC-specific (ffiec_call_report, ffiec_compare_banks, ffiec_coverage, ffiec_line_item, ffiec_search_banks). The remaining 36 tools are a generic Pipeworx data platform covering everything from Polymarket arbitrage to npm dependency scanning to AI visibility checks. An agent connecting to this server for call report data would face severe ambiguity about which tools belong to the stated purpose, and several meta-tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) have heavily overlapping routing purposes.

The FFIEC tools follow a clean ffiec_* prefix pattern, and the Pipeworx tools mostly use snake_case verb_noun naming (ask_pipeworx, compare_entities, resolve_entity, scan_dependency). However, the set mixes several naming styles: ffiec_* domain prefix, pipeworx_* platform prefix, bare verbs (remember, recall, forget, subscribe, unsubscribe), and descriptive phrases (kalshi_weather_edge, polymarket_kalshi_spread, release_calendar_markets). The inconsistency is not chaotic, but there is no single predictable pattern across the set.

41 tools is far too many for a server whose stated purpose is FFIEC Call Reports. Only 5 tools relate to the domain; the other 36 are unrelated Pipeworx platform tools (prediction markets, npm packages, AI visibility, memory, subscriptions, llms.txt generation). This is an extreme scope mismatch — the server name promises a focused domain, but the tool surface is a general-purpose data platform.

For the FFIEC domain itself, the coverage is solid: search banks, get a call report, compare banks, track a line item over time, and check data coverage. The main gap is that there is no obvious way to get a bank's full history in one call (line_item tracks one metric at a time), and there is no export or bulk download tool. But the core read/compare/trend workflows are covered. The unrelated tools do not help or hurt FFIEC completeness, though they add noise.