No user-submitted related servers found.
Scored across 19 tools
Most tools have clearly distinct purposes: registry lookup (find_company/get_company), reference knowledge (get_playbook/get_rules/get_escalation/get_context), case lifecycle (case_*), and billing (bill_*). The one real overlap is get_playbook, which already bundles the escalation ladder and channels that get_escalation returns separately, and the playbook/rules split (issue-scoped vs full text) requires reading descriptions carefully. find_company vs get_company is disambiguated well by their descriptions.
All names are snake_case, but the verb position flips between verb-first (find_company, get_rules, list_issues) and noun-first namespacing (case_open, case_list, bill_check, followups_due, scam_check). The domain prefixes are systematic and readable, yet direct inconsistencies exist, e.g. list_issues vs case_list for the same list verb, and case_get vs get_company for the same get verb.
Nineteen tools is on the heavy side of the ideal 3-15 band, but each group (discovery, playbook/rules knowledge, case tracking, bills, scam screening, data-quality feedback) maps to a real step in an escalation workflow. No tool looks like filler, though the knowledge-lookup cluster could be consolidated.
Coverage is broad and lifecycle-complete for the core loop: find a company, get a playbook, open/log/list/close a case, check follow-ups, draft the next message, and record bills. Gaps are minor but real: no way to edit or delete a case log entry, no bill listing/lookup by case, and find_regulators returns a list with no companion tool to fetch a single regulator's detail.