Teamspective

Returns engagement survey comments and open-text responses. Use this to understand the "why" behind engagement scores. **PREREQUISITE: Call get_user_context first** to confirm the user has access to engagement comments. **When to use:** - After seeing low or concerning scores in get_engagement_results - "What are people saying about [topic]?" - "Show me recent feedback comments" - "Why is [metric] score low?" - look at related comments - Preparing for team discussions or action planning **What you get:** - Comment text with question context - Date and recency (latest survey indicator) - Sentiment analysis (Positive or Negative when available) - Reply count for each comment - Grouped by question for easy reading **Filtering options:** - Filter by team (same as get_engagement_results) - Filter by specific question, theme, or KPI (recommended for topic-based queries) - Text search for specific words (use with caution - see below) - Adjust time period to see older/newer comments **Text search limitations (search_text parameter):** - Literal text matching only, not semantic/AI search - Case-insensitive but language-dependent - Comments are often in the workspace's local language (Finnish, Swedish, etc.) - Searching English terms in non-English workspaces will return no results - Prefer question/theme/kpi filters for topic-based filtering **Privacy:** - Comments are anonymous - no author information - Visibility rules are respected (workspace/team/admin-only) - Only shows comments the user is authorized to see **Example workflow:** 1. Call get_engagement_results → see "Workload" score is 54 (low) 2. Call get_engagement_comments with question: "Workload" to understand why 3. Summarize themes from comments for actionable insights **Examples with exact parameters:** - "Recent comments" → { "time_period_days": 30 } - "Comments about workload" → { "question": "Workload" } (preferred) - "Leadership theme feedback" → { "theme": "Leadership" } - "Engineering team comments" → { "team": "Engineering" } - "Wellbeing KPI feedback" → { "kpi": "Wellbeing" } - "Comments mentioning 'manager'" → { "search_text": "manager" } (use sparingly, language-dependent)

Returns engagement survey results for a team including KPIs, themes, questions, trends, and AI-ready insights. **PREREQUISITE: Call get_user_context first** to get the user's home team ID and see which teams they can access. This tool requires a valid team ID or name. **When to use:** - "How is my team doing?" or "What are our engagement trends?" - Questions about specific metrics: "leadership score", "psychological safety", "wellbeing" - "What needs attention?" or "Where are we struggling?" - Comparing current vs previous survey results **Understanding the data:** - Scores are 0-100 (higher is better). Industry average is typically 65-75. - Trends show change from previous survey period (e.g., "+5" means 5 points improvement) - KPIs are high-level metrics: Overall Engagement, Leadership, Wellbeing, DEIB - Themes are components under KPIs: Psychological Safety, Recognition, Growth, etc. - Questions are individual survey items that make up themes - "Redacted" means insufficient responses (<4) to protect anonymity **Insight labels (pre-interpreted for you):** - 📈 Trending up / 📉 Trending down: Significant change vs last period - ✅ Above benchmark / ⚠️ Below benchmark: Compared to industry average - 💪 Stronger/Weaker than workspace: Team vs company average **Common errors:** - "No team found matching X": The team name doesn't exist or user lacks access. Call get_user_context to see available teams. - "You don't have access to team X": User lacks permission for that team's engagement data. - "No engagement survey results available": Team hasn't completed surveys yet. **Historical questions:** By default, only questions asked within the current survey window are shown, matching the UI. Questions from older surveys (before the survey window started) are hidden unless you set include_historical=true. **Examples with exact parameters:** - "How is my team doing?" → { } (uses workspace default, but prefer getting team ID from get_user_context first) - "Engineering team engagement" → { "team": "Engineering" } or { "team": 12345 } - "Quick summary without questions" → { "include_questions": false } - "Just the scores, no insights" → { "include_insights": false } - "Show all questions including historical" → { "include_historical": true }

Returns feedback data for the user or their direct reports. Includes growth feedback, praise, and performance evaluations with full text content. **PREREQUISITE: Call get_user_context first** to confirm if the user is a manager (has direct reports) before using target: "direct_reports". **When to use:** - "Show me my feedback" or "What feedback have I received?" - "How is [person] doing?" (for direct reports) - "Team feedback summary" or "feedback trends" - Preparing for 1-on-1s or performance discussions **Understanding feedback types:** - Growth feedback: Developmental feedback with specific observations and suggestions - Praise: Recognition and positive feedback - Evaluations: Structured performance review responses (from 360 reviews, etc.) **What you get:** - Full text content of each feedback item - Provider name (who gave the feedback) - Timestamp and topic/category - Feedback type (growth, praise, evaluation) **Permissions:** - Users can always see their own feedback (target: "self") - Viewing direct reports' feedback requires manager access enabled by workspace admin - If user has direct reports but can't see their feedback, it's a workspace permission setting **Common errors:** - "No direct reports found matching X": The name doesn't match any of your direct reports. Use get_user_context to see your direct reports. - "User ID X is not one of your direct reports": The ID doesn't belong to your direct reports. - "You don't have permission to view feedback for X": The user is your direct report but workspace settings don't allow viewing their feedback. **Examples with exact parameters:** - "My recent feedback" → { "target": "self", "time_period_days": 30 } - "Sarah's feedback" → { "target": "direct_reports", "direct_report": "Sarah" } - "Feedback for user 12345" → { "target": "direct_reports", "direct_report": 12345 } - "All team feedback this quarter" → { "target": "direct_reports", "time_period_days": 90 }

Returns the authenticated user's identity, role, teams, and data access permissions. **IMPORTANT: Call this tool first** before using other Teamspective tools. It provides essential context about who you're speaking with and what data they can access. **When to use:** - START OF CONVERSATION: Always call this first to understand the user's context - Before calling get_engagement_results (to know which teams they can query) - Before calling get_feedback with target: "direct_reports" (to confirm they're a manager) - When user asks "who am I?", "what's my team?", or about their profile **Returns:** - Identity: name, email, numeric user ID - Role: "Manager" (has direct reports) or "Individual Contributor" - Profile attributes: job title, department, location (from HRIS, if available) - Home team: their primary team with team ID (use this ID in other tools) - Direct reports: list with names, emails, and user IDs (if manager) - use these IDs with get_feedback - Teams: all teams they belong to with team IDs - Engagement access: count of teams they can query for engagement results **Key concepts:** - "Workspace" = the organization/company in Teamspective - "Team" = a group within the workspace (e.g., Engineering, Sales) - "Home team" = the user's primary team, used as default when no team is specified - Team IDs are numeric (e.g., 12345) and more reliable than team names for queries **Example:** User says "How is my team doing?" → First call get_user_context to get their home team ID, then call get_engagement_results with that team ID.