No user-submitted related servers found.
Scored across 138 tools
Most tools target a clearly distinct resource+action combination, and the per-entity CRUD/search patterns are easy to tell apart. However, the qbo_expenses_* tools (list_purchases, get_purchase, get_bill) overlap with the standalone qbo_purchases_* and qbo_bills_* tools, creating genuine ambiguity about which to call. This is a limited but real boundary problem across an otherwise well-separated set.
Every tool uses the same qbo_<entity>_<action> snake_case convention with predictable verbs (list, get, create, update, search, void, send, upload). Deviations like qbo_expenses_list_purchases are still readable and follow the same overall scheme. No mixed conventions or camelCase are present.
With 138 tools this is far beyond any practical agent-facing surface and falls into the extreme-mismatch band. Even though QuickBooks has many entities, exposing every CRUD permutation individually is unwieldy and defeats discoverability. A domain-grouped or query-style interface would be far more appropriate.
Coverage is broad across sales, purchases, banking, lists, and reports, including less common entities like transfers, time activities, and attachables. Gaps remain: no general delete operations (only void for invoices/payments), no QBO query/batch endpoint, and no send/void for several document types. These are minor workarounds rather than dead ends.
