No user-submitted related servers found.
Scored across 14 tools
All tools have distinct and clearly defined purposes. There is no overlap; even search tools are differentiated by search term vs. filter-based search, and pipeline tools are separated by granularity. An agent can easily select the correct tool.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_lead, get_current_user, search_leads). Even longer names like parse_datetime_to_utc_iso_tool adhere to the pattern. No mixing of styles.
With 14 tools, the server is well-scoped for a CRM. It provides sufficient coverage of lead management, search, pipeline stages, and utility functions without being bloated. Each tool serves a necessary purpose.
The tool surface covers core lead lifecycle (create, get, update, search) and supporting operations (pipeline lookup, user/product lookup, datetime parsing). The only noticeable gap is the absence of a delete_lead tool, which agents would need for full CRUD. Otherwise, completeness is strong.