Scored across 5 tools
Each tool maps to a distinct resource and action: wanted status, individual debts, legal entity debts, proceeding details, and health check. The descriptions explicitly separate the wanted search from the open proceedings search, eliminating confusion.
The naming follows a clear check_* pattern for searches and get_ for detail retrieval. The only deviation is ping, which is a standard health-check name but does not match the verb_noun convention.
With 5 tools, the server is tightly scoped to the FSSP domain and every tool serves a clear purpose. The count feels appropriate for a focused read-only compliance server.
The core FSSP query surface is covered: individual debts, legal entity debts, wanted persons, and detailed proceeding lookup. A user can list proceedings and then fetch details by number, so the workflow has no obvious dead ends.