delimit

Official

Overview Schema Source Related Servers Score Discussions Admin

Delimit Soul Capture

delimit_soul_capture

Capture session state as a portable soul for cross-model resurrection, including git state, active tasks, decisions, and blockers. Use at session end or when context fills to enable seamless continuation in any model.

Instructions

Capture session state as a 'soul' for cross-model resurrection.

When to use: at session end or when context gets full, to save what you're working on so the next session in any model can pick up where you left off. When NOT to use: for general memory writes (use delimit_memory_store) or full handoff orchestration (delimit_session_handoff).

Sibling contrast: delimit_session_handoff writes a structured handoff for the next session; this writes a richer "soul" with git state and active task pointers, used by delimit_revive.

Side effects: writes a soul record via ai.session_phoenix.capture_soul. Auto-detects git state and the current model. Plain strings become one entry (with embedded commas preserved); native/JSON lists carry multiple entries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`blockers`	No	Blockers as one string, a native list, or a JSON list string.
`decisions`	No	Key decisions as one string, a native list, or a JSON list string.
`next_steps`	No	Next steps as one string, a native list, or a JSON list string.
`active_task`	No	What you're currently working on (one line).
`key_context`	No	Important context as one string, a native list, or a JSON list string.
`task_status`	No	One of "in_progress", "blocked", "almost_done".	in_progress
`tokens_used`	No	Estimated tokens consumed this session.
`project_path`	No	Project path to capture the soul for. Empty = auto-detect from cwd.
`context_fullness`	No	0.0-1.0 representing context-window fullness.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed12 schema fields changedv4.18.8Sep 8, 2026

addedInput schema / properties / blockers / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / blockers / description

Previous value: -"Comma-separated blockers."New value: +"Blockers as one string, a native list, or a JSON list string."

removedInput schema / properties / blockers / type
```
Removed value: -"string"
```

addedInput schema / properties / decisions / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / decisions / description

Previous value: -"Comma-separated key decisions made this session."New value: +"Key decisions as one string, a native list, or a JSON list string."

removedInput schema / properties / decisions / type
```
Removed value: -"string"
```

addedInput schema / properties / key_context / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / key_context / description

Previous value: -"Comma-separated important context for next session."New value: +"Important context as one string, a native list, or a JSON list string."

removedInput schema / properties / key_context / type
```
Removed value: -"string"
```

addedInput schema / properties / next_steps / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / next_steps / description

Previous value: -"Comma-separated next steps."New value: +"Next steps as one string, a native list, or a JSON list string."

removedInput schema / properties / next_steps / type
```
Removed value: -"string"
```

Changed1 schema field changedv4.13.2Sep 5, 2026

addedInput schema / properties / project_path

Added value: +{
+  "default": "",
+  "description": "Project path to capture the soul for. Empty = auto-detect from cwd.",
+  "type": "string"
+}

Changed2 schema fields changedv4.7.9Jun 9, 2026

changedInput schema / properties / context_fullness / description

Previous value: -"0.0-1.0 how full the context window is."New value: +"0.0-1.0 representing context-window fullness."

changedInput schema / properties / task_status / description

Previous value: -"in_progress, blocked, or almost_done."New value: +"One of \"in_progress\", \"blocked\", \"almost_done\"."

Addedv4.5.5May 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses the side effect: 'writes a soul record via ai.session_phoenix.capture_soul.' It also mentions auto-detection of git state and current model, providing transparency about its behavior beyond the readOnlyHint false annotation.

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-structured with clear sections: purpose, when to use, when not to use, sibling contrast, side effects, and a note on parameter format. It is concise and includes only relevant information without redundancy.

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 provides sufficient context for an agent to decide when to call this tool, including specific use cases, alternatives, and side effects. It also distinguishes it from the sibling delimit_session_handoff, ensuring the agent can choose the correct tool.

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

Parameters4/5

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

The schema descriptions cover all parameters (100% coverage). The description adds a useful note about how plain strings versus lists are handled ('Plain strings become one entry...'), which clarifies the behavior for list-accepting parameters. However, it does not detail each parameter individually beyond the schema, so it provides moderate added value.

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 tool's purpose: 'Capture session state as a soul for cross-model resurrection.' It also explains when to use it, which distinguishes it from other tools.

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?

It explicitly provides usage guidance: 'When to use: at session end or when context gets full' and 'When NOT to use: for general memory writes (use delimit_memory_store) or full handoff orchestration (delimit_session_handoff).' This gives clear criteria and alternatives.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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