No user-submitted related servers found.
Scored across 28 tools
Every tool maps to a distinct resource/action pair (list vs get, client vs job vs material, etc.), and even similar resources like client contacts and job contacts are clearly differentiated in descriptions. search and search_by_type are also distinct enough from the list tools.
The naming follows a consistent list_<plural_resource> / get_<singular_resource> convention with snake_case throughout, and search/search_by_type use the same verb-first style. There are no mixed casing or varying verb patterns.
At 28 tools, the set exceeds the 25+ threshold and feels heavy, especially since most are mechanical list/get pairs for the same entity types. The broad read-only scope explains the count, but it is more than an agent typically needs for a single server.
The server covers read operations for many ServiceM8 entities, but there are no create/update/delete tools at all, so any workflow that needs to modify a job, client, contact, or payment dead-ends. Some resources also have incomplete get/list coverage (e.g., staff has get but no list; attachments list only).