wiserwork

Fetch action items (tasks) from the user's wiserwork meetings — either across all meetings (omit meetingId) or for a single meeting (pass meetingId, resolved via list-meetings). Each item includes its title, description, assignee, due date, and completion status. Use this for requests like "what are my open action items" or "what tasks came out of the planning meeting".

get-action-items

Fetch the AI-generated summary (TL;DR, discussion points, and decisions) for one or more wiserwork meetings the user has access to. Resolve meeting ids via list-meetings first, then pass them here. Use this for requests like "summarize yesterday's standup" or "what was decided across this week's meetings". Each meeting without a ready summary carries a "status" explaining why (still processing, failed, or not recorded).

get-summary

Fetch the full transcript for a meeting the user has access to, as pipe-delimited rows ("start_timestamp|end_timestamp|speaker|text"). Resolve the meetingId via list-meetings first.

get-transcript

List the authenticated user's calendar meetings synchronized into wiserwork from their connected Google Calendar or Microsoft Outlook account. Use this for questions about the user's meeting calendar, calls, standups, 1:1s, schedule, or agenda, including ordinary requests such as "What's on my calendar?", "What meetings do I have today?", "What's my next meeting?", and "What were my last meetings?". The user does not need to name wiserwork in the request. Results include past, live, and upcoming scheduled meetings as well as meetings with captured content. To answer "upcoming"/"next"/"past"/"last"/"current" questions, pass the "timing" filter ("upcoming" | "live" | "past") rather than trying to guess a date range — it is applied server-side, so with a "limit" it returns the relevant meetings (the nearest upcoming, or the most recent past), and a meeting currently in progress counts as "live" (never "upcoming" or "past"). Use from/to only to bound an explicit window. Times are returned as UTC ISO 8601 timestamps. The user's timezone is Europe/Athens — convert times into that zone when talking to the user, and reason about "today"/"this week" in it. Date-only from/to values you pass are interpreted in that timezone. Call this FIRST to resolve which meeting the user means from natural language (e.g. "yesterday's standup", "today's meetings") before calling get-transcript / get-summary / get-action-items, then pass the returned "id". If no meetings are returned, surface the "note" field to the user. Read each meeting's "state" to know what content exists: - scheduled / live — hasn't produced content yet (it hasn't happened, or is in progress). - ended — was NOT recorded (no bot joined the call or it was not admitted); no recording, transcript, or summary exists or ever will. Tell the user nothing was captured for it. - processing — was recorded and is being processed now; content may not be ready yet, so tell the user to check back shortly. - processed — recording, transcript, and summary are available via get-transcript / get-summary / get-action-items. Only "processing"/"processed" meetings include the "hasRecording"/"hasTranscript"/"hasSummary" flags and "recordedDurationMinutes" (actual recorded length, null when not yet known). "scheduledDurationMinutes" (planned calendar length) and "timing" (past | live | upcoming) are always present.

list-meetings