Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Revive

delimit_revive
Read-onlyIdempotent

Restore the prior session's captured context—active tasks, decisions, blockers, and next steps—into any model at startup. Resume work without re-explaining.

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; calls ai.session_phoenix.revive.

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. Dates show when Glama detected each change.

  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.5/5.0
Behavior4/5

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

The annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds useful context by explicitly stating the operation is read-only, that it reads and applies the soul, and that it is cross-model. This aligns with and supplements the annotations without contradicting them.

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

Conciseness5/5

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

The description is well-organized with front-loaded purpose, concise when/where/contrast sections, and a short side-effects note. Every sentence adds value, and the formatting makes scanning easy.

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

Completeness5/5

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

The description covers when to use, when not to use, sibling contrast, side effects, and model scope. With a rich output schema and full parameter documentation in the input schema, nothing critical is missing for an agent to invoke this tool correctly.

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?

The input schema descriptions cover 100% of the three parameters, including defaults and empty-string meanings. The description itself adds no parameter-specific detail, but because the schema carries the full burden, the baseline of 3 is appropriate.

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 states a specific action ('Revive the last session's captured soul') and clearly distinguishes it from sibling tools like delimit_soul_capture and delimit_memory_recent. The unique resource ('soul') and the intent ('any model') are immediately clear.

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?

The description explicitly states when to use ('at session start'), when NOT to use (capturing a soul or reading recent memories), and names the alternative tools. It also contrasts with delimit_soul_capture, giving the agent unambiguous routing guidance.

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/delimit-ai/delimit-mcp-server'

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