Skip to main content
Glama
templetwo
by templetwo

where_did_i_leave_off

Resume work by retrieving spiral status, unconsumed handoffs, recent threads, and insights since last reflection. Optionally filter by domain tags and project for contextual resonance.

Instructions

Boot-up call. Answers 'where am I?' in one breath. Returns spiral status, unconsumed handoffs from previous instances (surfaced once, attribution-framed), recent open threads, and insights since last reflection. Read this first when resuming work. Handoffs flip to consumed=true after this call — they stay queryable via recall_insights but don't re-surface and pile up. Pass domain_tags (and optionally project) to also surface context-matched threads, mistakes-to-avoid, and related insights ranked by relevance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadNoOptional thread filter. Omit for all threads.
consumeNoMark surfaced handoffs as consumed. Set false for read-only preview.
source_instanceNoWhich instance is reading (recorded as consumed_by for audit).
domain_tagsNoOptional active domain tags for the work about to begin. When provided, adds a CONTEXTUAL RESONANCE section with the most relevant threads, mistakes, and insights ranked by tag overlap + recency.
projectNoOptional project name for additional match bonus in contextual resonance.
full_contentNoWhen true, surface insight content, self-model observations, open thread questions, and uncertainties in full — no truncation. Default false preserves boot brevity. Use true when you need to read addressed-letter insights or full self-model drift entries.
compactNoWhen true, omit the BEFORE YOU BEGIN preamble, the VOICES IN THE BOOT orientation block, and REFLECTOR'S MARGINALIA. Reduces boot token cost by ~40%%. Recommended for Haiku and repeat sessions where the preamble is already internalized. Still surfaces spiral status, lineage letters, handoffs, threads, activity, and self-model.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description reveals key behaviors: handoffs are marked consumed by default (unless consume=false), consumed handoffs remain queryable via recall_insights, and compact mode reduces token cost by ~40%. Discloses side effects of the call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two paragraphs with efficient structure. Front-loaded key purpose. Some redundancy ('in one breath') but overall well-organized for a complex tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers output components (spiral status, handoffs, threads, insights, contextual resonance) without an output schema. Explains behavior of key parameters. Missing explicit return format details, but adequate for a boot-up tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description adds significant meaning beyond field names: explains that domain_tags triggers a contextual resonance section, project adds match bonus, full_content controls truncation level, and compact omits preamble sections for efficiency.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states this is a boot-up call that returns spiral status, unconsumed handoffs, recent open threads, and insights. It distinguishes from siblings like 'recall_insights' by being the initial resume tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Read this first when resuming work.' Mentions handoffs becoming consumed and queryable via recall_insights, providing guidance on when to use alternatives. However, no explicit 'when not to use' statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/templetwo/sovereign-stack'

If you have feedback or need assistance with the MCP directory API, please join our Discord server