Related Servers

The vast surface is still largely partitioned by resource+action, and descriptions actively steer between near-neighbors (getPersonByEmail vs listPeople, searchPeopleByTag vs listPeople, removeTagFromPerson vs updatePerson, bulkUpdatePeople vs updatePerson, templates vs text message templates vs email campaigns). A few genuine overlaps remain — checkDuplicate vs getPersonByEmail, listCustomFields vs listDealCustomFields vs listStages, and getReactions/getThreadedReplies that only fetch by ID while listing lives elsewhere — but on the whole an agent can pick correctly.

The dominant pattern is verb_noun camelCase (listPeople, createDeal, updateAppointment, getWebhook), applied across nearly all 136 tools. Deviations are minor: namespace-prefixed tools (inboxAppAddMessage, inboxAppInstall, listInboxAppInstallations), plural names for single-item getters (getReactions, getThreadedReplies), the Em abbreviation (listEmEvents, createEmCampaign), and non-verb utility tools (about, help).

136 tools is far past the point where a single agent can hold the surface in mind, even though the underlying Follow Up Boss CRM is genuinely sprawling (people, deals, pipelines, appointments, automations, inbox apps, teams, ponds, webhooks). Many resources contribute 4-5 near-identical CRUD variants, so the count is defensible in principle but overwhelming in practice; splitting or namespace-scoping would help considerably.

Coverage is unusually broad: CRUD across people, deals, tasks, appointments, notes, calls, pipelines, stages, groups, teams, ponds, webhooks, automations, action plans, custom fields, plus specialized lookups. Gaps are mostly deletions (no delete tools for any resource), missing list operations for attachments and reactions/threaded replies (only get-by-ID), and no update paths for people's source/sourceUrl, but these are largely upstream API limitations rather than oversights.