No user-submitted related servers found.
Scored across 29 tools
Most tools target a clearly distinct resource and action (research_company records facts, get_company reads the record, draft_offer vs publish_offer are cleanly separated, get_traffic vs get_user_activity are explicitly differentiated). A few pairs are easy to blur: get_company_context vs add_project_context vs get_project_context, and get_updates vs get_project_messages, but the long descriptions usually resolve the choice.
The set is overwhelmingly lowercase snake_case verb_noun (get_, list_, add_, set_, draft_, publish_, decline_). Deviations are minor but noticeable: trood_whoami inverts the pattern (noun_verb), and show_my_trood_data / get_claude_md_block carry odd prefixes.
At 29 tools the surface is heavy for one server, even though it clusters into coherent domains (company research and offers, Product Engine projects, session/workspace, help levels and analytics, technology tree, admin reporting). Splitting admin analytics and the technology tree into their own server would cut the surface roughly in half.
The company/offer lifecycle is well covered end to end (research, add_fact, get_company, get_catalog, draft, publish, list_my_offers). The project side is read-mostly: there is no create_project, no way to post a project message, and no update to milestones or payments, which are likely agent dead ends; there is also no edit or delete for recorded facts.