use_context
Use Work Context ·read-only · non-destructive · idempotent · closed-world
Operate a Work Context in one of five modes: a lens over your memories.
A Work Context is a saved, source-grounded package for a job-to-be-done
(e.g. “3ngram GTM”, “Engineering Implementation”). This tool resolves the
context’s membership for you — the requesting user — and then dispatches
to one of five existing surfaces, scoped to that resolved membership.
SECURITY INVARIANT — a Work Context is a lens, not an access grant.
Resolution always runs inside your own visibility predicate. A memory you
cannot already see is NEVER returned by ANY mode, even when it has been
pinned into a context that is shared with you. Adding a memory to a shared
context can only organize memories you could already see; it can never
widen who can see that memory.
Modes (dispatch target):
search— search across the context’s resolved memories (default).brief— a session briefing assembled over the context.execute— task-relevant context compiled for the work at hand (passtaskto describe it; defaults to the context’s purpose).monitor— blockers, overdue, and stale items scoped to the context.delegate— a portable handoff package scoped to the context.
instructions and per-mode mode_config tuning are
surfaced as a header on the dispatched output.
Returns: str
Source: backend/src/engram/mcp/tools/work_context.py
Parameters
work_contexts.id (UUID) of a context you can see.One of
search / brief / execute / monitor / delegate. Defaults to search.Optional task description for
execute mode. Ignored by other modes; defaults to the context’s purpose when omitted.Optional project filter passed through to the dispatched surface (
brief / monitor / execute / delegate).Optional result cap for
search mode (defaults to the full resolved candidate set).