Return the current UTC time. Use this to anchor relative date references like 'today', 'yesterday', or 'last week' when the user does not provide an explicit date.

List activities in a time window with optional source/type/person filters. Returns shallow rows (no body); use get_activity to fetch full content.

Count activities in a time window, optionally grouped by source, type, identity, day, or week. The primitive behind 'how many', 'how often', and 'compare X vs Y' questions.

Keyword search (FTS5) over activity titles and content. Use this for concrete terms and phrases like 'deploy decision' or 'retry strategy'. Prefer this over semantic_search_activities for keyword-shaped queries.

Vector similarity search over activities. Use only when keyword search fails — for fuzzy or paraphrased queries like 'when did I work on the thing about latency'. Returns shallow rows ranked by similarity.

Fetch the full activity row (including content and metadata) for a given activity ID. Use after list_/search_ to drill into a specific row.

Find activities that share a ticket key with the given activity — e.g. given a Jira ticket, returns the commits / PRs / Linear issues / Confluence pages that reference the same key. Use this to assemble the full timeline around one piece of work.

Fetch a work item (a ticket or PR and everything linked to it) with its full cross-source timeline: the ticket, its commits, PRs, reviews, and discussions in chronological order. The best tool for 'show me everything about PROJ-123'.

List work items (tickets/PRs with their linked activity), most recently active first. The structural answer to 'what was I working on last week' — each item groups a ticket with its commits, PRs, and discussions. Use get_work_item for the full timeline of one item.

Activities authored by a specific person, optionally narrowed by a keyword query and date range. Pass identity_id if you have one (from list_identities/resolve_person); otherwise pass name_or_email and the tool resolves it.

Find decision-shaped activity in a date range: manual notes (type=note) merged with anything whose title or body hits decided/decision/RFC/ADR. Use this before answering 'what did we decide about X' or composing a quarterly summary.

Brief for a calendar meeting: returns the event details plus each attendee's recent shipped activity. Look up by activity_id if known, otherwise by date+title_contains. Use this to walk into a 1:1 or sync knowing what everyone's been doing.

Record a manual note — a decision, in-person conversation, observation, or anything else worth remembering. Stored as type=note from source=manual and indexed alongside everything else. Use this when the user dictates context you want recallable later.

List pre-built periodic summaries (daily/weekly/monthly/quarterly). Prefer these over re-summarizing raw activities when answering 'summarize my Q1' or 'what happened last week'.

Fetch a single pre-built summary by period type and start date. Returns null if no summary exists for that period.

List people known to the system (Git authors, Slack users, etc.), optionally filtered by a name/email substring.

Resolve a name or email to a single identity (the closest match). Returns the matched identity or null if no candidate is found.