Lattice

Use this to get the full chain of managers above an employee — from their direct manager up to the org root — when you need to understand reporting structure or escalation paths. Returns each ancestor's employee profile (entity ID, name, title, email) ordered from direct manager to org root. Only returns upward ancestors; does not include the employee themselves, their direct reports, or peers. Results reflect what the user is permitted to see.

Searches for employees in the user's company by name, work email, and/or department. Use this when you need to look up a person's identity or resolve a name to an entity ID before calling another tool. Returns employee profiles including their entity ID (UUID), which is the identifier required by other tools that accept employee ID parameters. Omit all filters to list all employees. Does not return org-chart relationships (reports, manager chain) or work artifacts (reviews, feedback, goals). Results reflect what the user is permitted to see.

Retrieves feedback items the user has visibility into. It should be used when the user wants to see what others have said about a specific employee, or what feedback a specific employee has written about others. Each item includes the feedback text, visibility level, creation date, author and target identities (UUID, name, email), and any company values tagged on the feedback. Pass aboutEmployeeId for feedback about a person, or byEmployeeId for feedback authored by them; if both are passed, aboutEmployeeId takes precedence. If neither is set, returns recent feedback accessible to the user. Does not return performance reviews, check-in/update answers, or 1:1 notes. Results reflect what the user is permitted to see.

Use this to surface past 1:1 meetings between the user and a specific employee as context for review-drafting, prep for an upcoming 1:1, or recalling what was discussed and committed to. Returns each meeting with its talking points, action items, shared notes, AI summary, and the user's own private note. Participant/creator/assignee identities are returned with name + email already resolved. Filter by dateFrom/dateTo to scope to a review period or other window. Only returns 1:1s the user themselves participated in; does not return meetings between other employees, future scheduled meetings, or meetings the user was not part of. Results reflect what the user is permitted to see.

Use this to get the team beneath an employee — direct reports, or the full subtree down to a given depth — when you need to understand who someone manages, fan out work, or analyze a team. Returns each report's employee profile (entity ID, name, title, email) with their manager's identity inline. Only returns downward reports; does not include the employee themselves, their manager, or peers. Results reflect what the user is permitted to see.

Retrieves reviews the user is permitted to see, filterable by who the review is about, who wrote it, the cycle, direction, submission/sharing status, and date range. It should be used when the user wants to read or browse past reviews - their own self-reviews, reviews they wrote about someone, shared reviews about an employee, or all reviews in a given cycle. Each result includes review metadata (id, cycle, reviewee identity, author identity, direction, state), the questions on the form, and the saved answers (text and ratings). By default returns only reviews that have been shared with the reviewee; pass `status` to broaden to all submitted reviews or to open drafts. Does not return open drafts the user is currently authoring or review cycle metadata without review content. Pagination is offset-based: `fullCount` reflects the total number of review packets matched (not the total number of review rows returned, since one packet can contain multiple reviews); `nextCursor`, when present, walks to the next page. Results reflect what the user is permitted to see.

Returns the user's current-period check-in (status update) draft, with the questions on the form, any answers already saved, the period bounds, and the cadence. Use this when the user wants to see, fill out, or edit their check-in for the current period - 'what's my weekly update look like?', 'show me what I need to fill in for my check-in', 'start my update for this week.' Returns the draft id (use it to save answers), the questions on the form, the period dates (start/end), the cycle cadence in weeks, the public flag, the saved sentiment, and the saved answers so far. If `draft` is null, no current-period draft exists yet — questions are still returned so the user can preview the template, but answers cannot be saved until a draft is available. Does not return other employees' updates or historical drafts.

Retrieves the open performance review drafts the user is currently authoring. Each draft includes the review cycle metadata, the questions on the form, any answers already saved, and identifying information about the reviewee (UUID, name, email). Each answer has a unique id that identifies the specific answer slot — multiple answer slots can share the same questionRevisionEntityId when a form rates several competencies or goals with the same question, but each slot always has its own id. This tool should be used when the user wants to see, fill out, or edit reviews they've been assigned — including self-reviews and reviews about other people. Does not return submitted or shared reviews, reviews authored by other people, or review cycle metadata without draft content. By default returns all open drafts authored by the user across all review cycles. Results reflect what the user is permitted to see.

Returns the review cycles the user is currently participating in, with their role (reviewee, reviewer, or both) and how many review drafts they owe per cycle. It should be used when the user wants to know which cycles affect them right now - 'what cycles am I in?', 'am I a reviewer or a reviewee in Q1?', 'which cycles am I behind in?'. Returns cycle-level aggregates only (counts), not the draft content itself. Each result includes the cycle id, name, type, state, start/end timestamps, the user's role in that cycle, and counts of open drafts authored by the user and shared reviews about the user. A cycle is considered 'reviewee participation' only once at least one review about the user has been shared - cycles where the user is enrolled as a reviewee but has not yet received a shared review do not appear under that role. Does not return cycles the user is not participating in, the questions on the form, or other reviewees in the cycle. To guard against runaway queries the underlying fetches are capped, so a user with extensive review history may see an incomplete cycle list; the response includes a `truncated` flag when this happens. When `truncated` is true, narrow the window with `dateFrom` / `dateTo` to fetch the missing cycles. Results reflect what the user is permitted to see.

Lists active departments in the user's company. Use this when the user asks about organizational structure or when you need a department entity ID to filter employees by department. Each department includes its entity ID (UUID) and name. Does not return the employees within each department or the department hierarchy. Results reflect what the user is permitted to see.