Related Servers

Most tools have clearly distinct purposes, with descriptions carefully differentiating between similar get_* analytics tools (e.g., get_analytics_summary vs get_study_insights vs get_sessions_report). The get_study vs get_study_summary pair is explicitly disambiguated, and report tools are scoped by participant/session/study. Only minor overlap exists among the various analytics read tools, but the guidance is strong.

The server follows a consistent get_*/create_*/update_*/delete_*/generate_* pattern, making most tool names predictable. Minor inconsistencies exist: list_studies vs get_sections/get_participants, and copy_study uses a verb not aligned with the standard create/update/delete set. Overall, the naming is coherent and readable.

With 42 tools, this server exceeds the 'too many' threshold of 25+ for the apparent scope. While the domain (UX research) is broad, many specialized analytics read tools (e.g., get_qualitative_insights, get_quantitative_data, get_qna_analysis) could potentially be consolidated. The high count will likely overwhelm agents and increase selection difficulty.

The tool set is very comprehensive: full study CRUD, sections with guide generation/editing, participant and session retrieval, analytics generation and multiple read views, report generation, synthesis chat, tags, and Figma integration. Minor gaps exist (e.g., no section reordering, no participant CRUD), but core workflows have no dead ends and dependencies are clearly documented.