No user-submitted related servers found.
Scored across 12 tools
Each tool targets a distinct resource and action: list/get pairs for accounts, balances, transactions, and events are clearly separated, and the invoice workflow tools (read, match, prepare, attach) occupy distinct stages. The only mild overlap is between transactions and events, but descriptions make the boundary explicit (posted bank movements vs. all events including unposted).
All 12 tools follow the same folio_ prefix plus snake_case verb_noun pattern (list_accounts, get_transaction, read_invoice, prepare_invoice_assignment, attach_invoice). No mixed conventions or vague verbs.
12 tools is well-scoped for an accounting/invoice-attachment workflow. Each tool earns its place: read access to accounts, balances, transactions, events, categories, invoices, and attachments, plus the three-step match/prepare/attach flow.
The core lifecycle from reading transactions/events through matching, preparing, and uploading an invoice attachment is covered end-to-end, including safety gates around upload approval. Minor gaps remain: no list_categories (only get_category by id), no explicit tool to verify upload outcome or list all attachments per event outside get_event, and no pagination for transactions.