Lawcus MCP by usefulapi

Most tools target a distinct resource+action (get vs list vs report are clear), and the report_* family is well separated from the list_* family by the Admin-role aggregation framing. The blurry spot is billing: lawcus_list_billing_items explicitly covers time entries, expenses and flat fees, overlapping with lawcus_list_time_entries and lawcus_list_expenses, so an agent may pick either path for the same data.

All 27 tools use a uniform lawcus_ prefix with snake_case verb_noun naming (create_/get_/list_/report_), making the pattern highly predictable. The only deviation is the bare lawcus_search, which lacks a noun while every other name states its resource.

27 tools is on the heavy side, though the breadth is partly justified by a broad legal-practice domain (contacts, matters, tasks, billing, leads, plus eight reports). The eight near-parallel report_* tools and three overlapping billing/time/expense listers push it past a well-scoped set.

The surface is overwhelmingly read-only: 25 of 27 tools are get/list/search/report, with writes only for contacts and tasks. Core lifecycle operations a legal PM agent would need are absent — create/update matter, log time entry, create expense, create/convert lead, and any update/delete at all — leaving unavoidable dead ends.