No user-submitted related servers found.
Scored across 36 tools
Most tools are clearly scoped to a single entity or sub-resource, but there is overlap between manage_status_page and manage_maintenance_window for publishing maintenance, and between discover_form_fields and get_fields actions on manage_ticket and manage_change. These overlaps could cause an agent to select the wrong tool for the same logical operation.
Every tool follows the consistent 'manage_<entity>' or 'manage_<entity>_<subresource>' pattern, using snake_case throughout. No mixed conventions or verb variations, making the naming highly predictable.
36 tools is on the high side, but the server covers a broad Freshservice domain including tickets, changes, problems, releases, assets, projects, status pages, and administrative entities. Each tool addresses a distinct resource cluster, so the count is reasonable despite being above the typical 15-tool threshold.
The tool surface is extensive, covering CRUD for most core entities, but notable gaps exist: solution articles have no delete action, canned responses are read-only only, and ticket tasks are not represented. These missing operations can force agents into workarounds or cause failures on complete workflow execution.