No user-submitted related servers found.
Scored across 70 tools
Most tools are clearly separated by entity type, but there is notable overlap between list, filter, and search tools for the same entities (e.g., get_assets vs search_assets vs filter_assets, get_changes vs filter_changes). An agent may struggle to choose the right variant.
All tools use a consistent snake_case verb_noun pattern (get_, create_, update_, delete_, filter_, search_). Even variations like get_ticket_by_id or get_agent_group_by_id are predictable and follow the same convention.
With 70 tools, this is far beyond the 50+ threshold for 'extreme mismatch'. The server tries to cover every Freshservice module, resulting in an overwhelming surface that is unlikely to be navigated efficiently by agents.
Tickets, changes, and assets have solid CRUD coverage, but many other entities (agents, groups, products, contracts, etc.) are read-only with no create/update/delete operations. This creates significant gaps where agents can retrieve data but cannot complete lifecycle workflows.