Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Revive

delimit_revive
Read-onlyIdempotent

Restore the previous session's captured context—active tasks, decisions, blockers, and next steps—into any model at session start.

Instructions

Revive the last session's captured soul in any model.

When to use: at session start, to load the prior session's soul (active task, decisions, blockers, next steps). When NOT to use: to capture a soul (delimit_soul_capture) or read recent memories (delimit_memory_recent).

Sibling contrast: delimit_soul_capture writes the soul; this reads and applies it (cross-model: Claude, Codex, Gemini, Cursor).

Side effects: read-only; uses Session Phoenix when installed, or the shipped Free session_continuity core for explicit local state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoOptional handoff/receipt id. When set, revives ONLY that scoped handoff context (for dispatched subagents) instead of the global session soul. Empty = full soul (default).
soul_idNoSpecific soul id to revive. Empty = latest.
project_pathNoProject path to revive. Empty = auto-detect from cwd.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.7.9
    • changedInput schema / properties / project_path / description
      Previous value: -"Project to revive. Auto-detects from cwd."New value: +"Project path to revive. Empty = auto-detect from cwd."
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "",
+  "description": "Optional handoff/receipt id. When set, revives ONLY that scoped handoff context (for dispatched subagents) instead of the global session soul. Empty = full soul (default).",
+  "type": "string"
+}
    • changedInput schema / properties / soul_id / description
      Previous value: -"Specific soul to revive. Empty = latest."New value: +"Specific soul id to revive. Empty = latest."
  2. Addedv4.5.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations: it mentions it uses 'Session Phoenix when installed, or the shipped Free session_continuity core' and notes cross-model applicability (Claude, Codex, Gemini, Cursor). This is extra behavioral detail not present in annotations, warranting a above-baseline score.

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?

The description is well-structured and front-loaded: it leads with the core action, then gives usage guidance, sibling contrast, and side effects. It is a bit longer than strictly necessary, but every sentence earns its place. Minor redundancy in the 'When NOT to use' section is acceptable.

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?

Given the presence of an output schema and full parameter coverage, the description is complete for an agent to invoke this correctly. It covers use context, exclusions, and side effects. Slight gap: doesn't explicitly state what the output contains, but the output schema covers that. Overall sufficient.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (scope, soul_id, project_path) have detailed descriptions in the schema. The tool description does not add extra meaning about parameters beyond what the schema provides, but it doesn't need to. Baseline 3 is appropriate when schema carries the load.

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 the verb 'Revive' and the resource 'last session's captured soul', and explicitly contrasts with siblings delimit_soul_capture (writes) and delimit_memory_recent (reads memories). An agent can immediately distinguish this tool from its siblings.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('at session start'), when-not-to-use (capture soul, read recent memories), and names the sibling alternatives. The sibling contrast is direct and unambiguous, leaving no inference needed.

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

Deploy Server

Other Tools